Google Chrome: Type confusion in V8 allows code execution in the sandbox
Summary
Chrome versions before 154.0.8037.97 contain a type confusion flaw in the V8 JavaScript engine (CVE-2026-103625, CVSS 8.8). An attacker can run arbitrary code inside the browser sandbox by luring a user to a crafted HTML page. Exploitation requires the user to visit that page, and the sandbox is still needed for full compromise.
Affected
- Google Chrome before 154.0.8037.97 (desktop)
- Chromium-based browsers and Debian chromium packages depend on their bundled V8 version; check each vendor's advisory
- The CVE record's affected range reads "154.0.8037.97 to < 154.0.8037.97", which is inconsistent; the description states "prior to 154.0.8037.97"
Fixed in
- Google Chrome 154.0.8037.97 (Windows, Mac and Linux, per Google's stable update of 1 October 2026; the snippet did not confirm the CVE by name)
- Google Chrome 154.0.8037.151 or newer Chrome 154 stable build (later ChromeOS release of 9 October 2026)
- Debian chromium 155.0.8059.39-1~deb12u1 for bookworm
Workaround
Unknown. No vendor workaround found. Until patched, limit browsing to trusted sites.
Exploitation
- No confirmed in-the-wild exploitation found; CISA SSVC lists exploitation as none and automatable as no
- No public proof-of-concept found
- EPSS is low (0.00317 in the Vulners snapshot)
- Not to be confused with CVE-2026-85046, a separate V8 type confusion bug that was exploited in the wild
Our recommendation
- Update all Chrome installations to the latest Chrome 154 stable build (or current stable) and verify the version on each endpoint
- Check that Edge, Brave, Opera and other Chromium-based browsers and embedded Chromium apps are updated
- Enable automatic browser updates and monitor patch status
- Priority is high for workstations, low for servers unless they run a browser or Chromium-based kiosk application
Public exploits
PoC-in-GitHub, Metasploit and Exploit-DB list nothing for this CVE.
Research sources
- Google Chrome Stable Channel Update for Desktop (1 Oct 2026) chromereleases.googleblog.com
- Google Chrome Stable Channel Update for ChromeOS (9 Oct 2026) chromereleases.googleblog.com
- Chromium issue tracker entry issues.chromium.org
- OSV record for Debian (DEBIAN-CVE-2026-103625) osv.dev
- NVD/CVE data via Vulners vulners.com
- Rapid7 summary via Vulners vulners.com
Researched and written up in English and German by an AI (Claude by Anthropic) based on NVD, CISA, EPSS and the sources listed. The vendor information is authoritative. Researched on 31 Oct 2026, 22:47.
Original description (NVD)
Type confusion in V8 in Google Chrome prior to 154.0.8037.97 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
Sources
The tracker combines official, freely usable data sources – updated continuously:
- NVD (NIST) – CVEs, rating (CVSS), affected products
- CISA KEV – vulnerabilities confirmed by CISA as actively exploited
- CISA Vulnrichment – CISA assessment (SSVC) in the official CVE record
- FIRST EPSS – probability of exploitation
- Microsoft MSRC – Patch Tuesday: vulnerabilities, severity, updates
- PoC-in-GitHub – public proof-of-concept repositories
- Metasploit (Rapid7) – modules of the Metasploit Framework
- Exploit-DB (OffSec) – archive of public exploits (links only)
- Patch days: official vendor pages (linked per vendor) (Vendor patch days)
This product uses data from the NVD API but is not endorsed or certified by the NVD. EPSS data © FIRST.org.
Affected? We can help.
We check whether your systems are affected, install updates and close the gap – continuously with the System Health Checker if you wish.