Google Chrome: Memory corruption in V8 JavaScript engine allows code execution
Summary
Memory corruption in the V8 JavaScript engine of Google Chrome allows a remote attacker to potentially execute arbitrary code inside the browser sandbox. The attack requires that a user visits a crafted HTML page, for example via a phishing link or a compromised website. Code execution inside the sandbox is serious, but a full compromise usually also requires a sandbox escape, and no such chain is known for this CVE.
Affected
- Google Chrome desktop prior to 156.0.8078.73 (per the CVE description)
- Affected Chromium-based browsers, such as Microsoft Edge, until their vendor releases the matching fix
- Chromebooks (ChromeOS): patch status unverified in the research sources
Fixed in
- Google Chrome 156.0.8078.73 or later (per research notes; the Google advisory was not verified directly)
- A newer Chrome 156 build (156.0.8078.79/.80) is reported by a secondary source; coverage of this CVE is unverified
- Microsoft Edge: fix pending according to the research notes; check for the matching build
Workaround
- No workaround is documented. Applying the update is the mitigation.
- Chrome must be restarted (Relaunch) after the update, otherwise the fix does not take effect.
Exploitation
- No confirmed exploitation in the wild, according to the reviewed sources.
- Not listed in the CISA KEV catalog at the time of research; the listing should be rechecked.
- No public proof-of-concept exploit found.
- Other 2026 Chrome V8 flaws were exploited, so the baseline risk for V8 bugs is elevated.
- CISA SSVC: Exploitation none, Automatable no, Technical Impact total.
Our recommendation
- Update all Chrome installations (desktop, Android, Chromebooks) to 156.0.8078.73 or later, preferably the latest 156 build.
- Check Microsoft Edge separately and install Microsoft's update when released.
- Confirm that the browser was restarted after the update.
- Monitor the CISA KEV catalog and Google's notices on exploits in the wild.
- Prioritise patching, because browsers are a common entry point and the update is free and quick to install.
Public exploits
PoC-in-GitHub, Metasploit and Exploit-DB list nothing for this CVE.
Research sources
- Google Chrome Releases: Stable Channel Update for Desktop chromereleases.googleblog.com
- Chromium issue tracker entry issues.chromium.org
- GitHub CVE tracker entry (KEV and EPSS data) github.com
- PiunikaWeb: Google Chrome 156 security update piunikaweb.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, 10:02.
Original description (NVD)
Memory corruption in V8 in Google Chrome prior to 156.0.8078.73 allowed a remote attacker to potentially 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.