CVE-2026-87491: Google Chromium V8 Out of Bounds Write
Google Chromium V8 · listed in the CISA catalog of actively exploited vulnerabilities since 2026-09-09.
- CVSS v3.1 (Debian)
- 8.8
- high
- EPSS (exploit probability, 30 days)
- 3.5%
- higher than 89.4% of all CVEs
- Added to CISA KEV
- 2026-09-09
- US federal due date 2026-09-23
- Ubuntu priority
- –
CVE-2026-87491 explained
CVE-2026-87491 is an out-of-bounds write in V8, the JavaScript engine in Chromium. A remote attacker can use a crafted HTML page to execute arbitrary code inside the browser sandbox. CISA lists it in its Known Exploited Vulnerabilities catalog, so prompt patching matters.
Impact
An attacker who gets a user to open a crafted HTML page can run arbitrary code inside the Chromium sandbox. The attack works over the network, needs low complexity and no privileges, but requires user interaction. Confidentiality, integrity and availability impacts are all rated high. The code runs within the sandbox, so the scope is unchanged. CISA has confirmed exploitation in the wild. Known ransomware use is listed as unknown.
Who is affected
The chromium source package is affected in Debian. Fixed versions are available in the standard archive for all listed releases. Debian 12 (bookworm) is fixed in 153.0.8010.52-1~deb12u1. Debian 13 (trixie) is fixed in 153.0.8010.47-2~deb13u1. Debian 14 (forky), the Debian testing distribution, is fixed in 153.0.8010.47-1. No Ubuntu releases are listed in the facts.
Written with AI from the data on this page and checked against it automatically.
Official description
Out of bounds write in V8 in Google Chrome prior to 153.0.8010.36 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: Medium)
CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements”. Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
CISA notes
Upstream versions (CVE record)
From the CVE record published by the vendor or CVE numbering authority.
- Google ChromeAffectedFixed in
- < 153.0.8010.36
- 153.0.8010.36
| Product | Affected | Fixed in |
|---|---|---|
| Google Chrome |
|
|
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.
Debian 14 (forky)·chromium
testing distribution
Fixed: 153.0.8010.47-1
Debian 13 (trixie)·chromium
Fixed: 153.0.8010.47-2~deb13u1
Debian 12 (bookworm)·chromium
Fixed: 153.0.8010.52-1~deb12u1
What to do
- Update the
chromiumpackage to the fixed version for your Debian release from the standard archive. - On Debian 12 (bookworm), install
153.0.8010.52-1~deb12u1or later; on Debian 13 (trixie), install153.0.8010.47-2~deb13u1or later. - Ask users to close and restart all Chromium windows so the patched code is loaded.
- Check that no hosts still run an older
chromiumversion, giving priority to hosts used for web browsing. - Follow the Debian advisory and CISA required action for this known exploited vulnerability.
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" ;; esac3. 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-787 Out of bounds write
Questions about CVE-2026-87491
- Is this vulnerability being exploited?
- Yes. CISA added CVE-2026-87491 to its Known Exploited Vulnerabilities catalog on 2026-09-09, with a US federal due date of 2026-09-23. Whether ransomware uses it is listed as unknown.
- Does installing the update protect running browsers?
- No. Running Chromium processes keep the old code until they are restarted. Users must close and reopen the browser after the package update.
- Can an attacker exploit this without user action?
- No. The CVSS vector requires user interaction. A user must open a crafted HTML page. No privileges are needed, and the attack can come over the network.
Written with AI from the data on this page and checked against it automatically.
References
Trackers and catalogs
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.