Skip to content
Server Security Center
KEVhigh8.8

CVE-2025-5419: Google Chromium V8 Out-of-Bounds Read and Write

Google Chromium V8 · listed in the CISA catalog of actively exploited vulnerabilities since 2025-06-05.

CVSS v3.1 (CVE record)
8.8
high
EPSS (exploit probability, 30 days)
7.6%
higher than 94.6% of all CVEs
Added to CISA KEV
2025-06-05
US federal due date 2025-06-26
Ubuntu priority
–

CVE-2025-5419 explained

CVE-2025-5419 is an out-of-bounds read and write flaw in the V8 JavaScript engine used by Google Chrome and Chromium before 137.0.7151.68. A remote attacker could use a crafted HTML page to potentially exploit heap corruption. The flaw is listed in the CISA Known Exploited Vulnerabilities catalog, so prompt patching matters.

Impact

A remote attacker who gets a user to open a crafted HTML page could potentially exploit heap corruption. No privileges are needed and attack complexity is low, but user interaction is required. The CVSS vector rates confidentiality, integrity and availability impact as high, with unchanged scope. CISA lists the flaw as known to be exploited; known ransomware use is marked unknown.

Who is affected

The facts cover one release. On Debian 12 (bookworm), a supported release, the chromium source package is affected. A fixed version, 137.0.7151.68-1~deb12u1, is available in the standard archive. No other Ubuntu or Debian releases are listed in the facts, so their status is not stated here.

Written with AI from the data on this page and checked against it automatically.

Official description

Out of bounds read and write in V8 in Google Chrome prior to 137.0.7151.68 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)

CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

CISA notes

Upstream versions (CVE record)

From the CVE record published by the vendor or CVE numbering authority.

  • Google Chrome
    Affected
    • < 137.0.7151.68
    Fixed in
    • 137.0.7151.68

Ubuntu and Debian releases

A server is vulnerable if it has a package built from the listed source package installed in a version lower than the fixed version for its release.

What to do

  1. Update the chromium package on Debian 12 (bookworm) to 137.0.7151.68-1~deb12u1 or later.
  2. Close and restart all running Chromium instances so the patched code is loaded.
  3. Confirm the installed chromium version on every system, including shared or kiosk machines.
  4. Follow the Debian security advisory for any further updates to chromium.

Written with AI from the data on this page and checked against it automatically.

Check and fix on a server

Run on each Ubuntu or Debian server. Replace chromium with the source package from the table above.

1. Show installed packages built from the source package, with their versions

dpkg-query -W -f='${binary:Package} ${Version} ${source:Package}\n' | awk '$3=="chromium"'

2. Compare each installed version with the fixed version for your release from the table

I=INSTALLED_VERSION; F=FIXED_VERSION   # replace both
dpkg --compare-versions "$I" lt "$F"; case $? in 0) echo vulnerable ;; 1) echo "fixed or newer" ;; *) echo "check the versions" ;; esac

3. Install the fix

sudo apt update && sudo apt install --only-upgrade $(dpkg-query -W -f='${binary:Package} ${source:Package}\n' | awk '$2=="chromium"{print $1}')

Services keep running the old code until they are restarted – restart the affected service or check with needrestart.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-125 Out-of-bounds Read, CWE-787 Out-of-bounds Write

Questions about CVE-2025-5419

Is this vulnerability being exploited?
Yes. CISA added CVE-2025-5419 to its Known Exploited Vulnerabilities catalog on 2025-06-05, with a US federal due date of 2025-06-26. Whether it is used in ransomware campaigns is listed as unknown.
Which version fixes the issue on Debian 12?
On Debian 12 (bookworm), the chromium package is fixed in version 137.0.7151.68-1~deb12u1, available from the standard archive.
Do I need to reboot after updating?
A reboot is not required for a browser update. However, running Chromium instances keep using the old code until they are closed and restarted.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.