CVE-2026-85046: Google Chromium V8 Type Confusion
Google Chromium V8 · listed in the CISA catalog of actively exploited vulnerabilities since 2026-09-04.
- CVSS v3.1 (CVE record)
- 8.8
- high
- EPSS (exploit probability, 30 days)
- 1.8%
- higher than 79.1% of all CVEs
- Added to CISA KEV
- 2026-09-04
- US federal due date 2026-09-18
- Ubuntu priority
- –
CVE-2026-85046 explained
CVE-2026-85046 is a type confusion flaw in the V8 JavaScript engine used by Google Chrome and Chromium. A remote attacker can execute arbitrary code inside the browser sandbox through a crafted HTML page. CISA lists it as known to be exploited, so affected systems should be updated promptly.
Impact
An attacker who gets a user to open a crafted HTML page can run arbitrary code inside the browser sandbox. The attack works over the network, needs no privileges and has low complexity, but requires user interaction. Successful exploitation can have high impact on confidentiality, integrity and availability within the affected browser process. CISA has added the flaw to its Known Exploited Vulnerabilities catalog. Known ransomware use is listed as unknown.
Who is affected
The chromium source package is affected on Debian 12 (bookworm), Debian 13 (trixie) and Debian 14 (forky). Fixed versions are available in the standard archive for all three: 152.0.7977.82-1~deb12u1 for bookworm, 152.0.7977.82-1~deb13u1 for trixie and 152.0.7977.82-1 for forky. Debian 14 (forky) is the Debian testing distribution, not a stable release. No Ubuntu releases are listed in the facts.
Written with AI from the data on this page and checked against it automatically.
Official description
Type confusion in V8 in Google Chrome prior to 152.0.7977.82 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
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
- < 152.0.7977.82
- 152.0.7977.82
| 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: 152.0.7977.82-1
Debian 13 (trixie)·chromium
Fixed: 152.0.7977.82-1~deb13u1
Debian 12 (bookworm)·chromium
Fixed: 152.0.7977.82-1~deb12u1
What to do
- Update the
chromiumpackage to the fixed version for your Debian release from the standard archive. - On bookworm, install
152.0.7977.82-1~deb12u1or later; on trixie, install152.0.7977.82-1~deb13u1or later. - Ask users to fully close and restart Chromium so the updated code is loaded.
- Verify the installed
chromiumversion on all desktops and shared systems. - Prioritize this update because the flaw is listed as known exploited by CISA.
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-843 Type confusion
Questions about CVE-2026-85046
- Is this vulnerability being exploited?
- Yes. CISA added CVE-2026-85046 to its Known Exploited Vulnerabilities catalog on 2026-09-04, with a US federal due date of 2026-09-18. Known ransomware use is listed as unknown.
- Does updating the package fix running browsers?
- No. Running Chromium sessions keep using the old code until the browser is fully closed and started again. Make sure users restart the browser after the update.
- Which Debian package versions contain the fix?
- Debian 12 (bookworm):
152.0.7977.82-1~deb12u1. Debian 13 (trixie):152.0.7977.82-1~deb13u1. Debian 14 (forky), the testing distribution:152.0.7977.82-1.
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.