Google Chrome: Memory corruption in V8 JavaScript engine allows code execution
Summary
The Google Chrome desktop browser contains a memory corruption flaw in the V8 JavaScript engine (CVE-2026-113192, CVSS 8.8). A remote attacker can use a crafted HTML page to execute arbitrary code inside the browser sandbox. No authentication is required, but the user must open the malicious or compromised page. The vendor does not claim a sandbox escape; a full compromise would normally need a second vulnerability.
Affected
- Google Chrome desktop before 156.0.8078.47 on Windows, macOS and Linux
- Vendor sources differ on the exact builds; treat all builds below the fixed versions as affected.
Fixed in
- Chrome 156 stable: 156.0.8078.47 (Linux) and 156.0.8078.48 (Windows, macOS), according to secondary sources; not verified against the vendor post
- Later stable update of 27 October 2026 (reported as 156.0.8078.73 or 156.0.8078.74): use the latest stable build
Workaround
- No vendor workaround known. Installing the fixed build is the remedy.
- Until updated, avoid untrusted websites and keep auto-update enabled.
- A browser restart is required after the update.
Exploitation
- No known exploitation in the wild at the time of research.
- CISA KEV status not verified.
- No public proof-of-concept found.
Our recommendation
- Update all Chrome installations to the latest stable build, not only 156.0.8078.47.
- Restart browsers and confirm the version on each endpoint.
- On Linux, check that the Chromium snap is refreshed; the chromium-browser wrapper package is not affected.
- Check Extended Stable systems separately.
- Monitor the Chromium bug tracker and CISA KEV for changes.
Public exploits
PoC-in-GitHub, Metasploit and Exploit-DB list nothing for this CVE.
Research sources
- Chrome Releases: Stable Channel Update for Desktop chromereleases.googleblog.com
- Chromium issue tracker entry issues.chromium.org
- NVD record via Vulners vulners.com
- Ubuntu security tracker ubuntu.com
- Chrome security update guide (October 2026) sandbanksdigital.com
- Chrome 156 security update overview (SecurityOnline) securityonline.info
- Chrome 156 security update (WindowsForum) windowsforum.com
- Mallory: Chrome 156 stories mallory.ai
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, 13:06.
Original description (NVD)
Memory corruption in V8 in Google Chrome prior to 156.0.8078.47 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.