Google Chrome: Memory corruption in API allows sandboxed code execution
Summary
Google Chrome before 156.0.8078.47 contains a memory corruption flaw in an API. A remote attacker can execute arbitrary code inside the browser sandbox by luring a user to a crafted HTML page. The attack requires no authentication but needs user interaction, such as opening the page.
Affected
- Google Chrome prior to 156.0.8078.47 (desktop)
- Chromium-based browsers that have not yet integrated the fix, such as Microsoft Edge, depending on their build
- Exact affected builds per vendor: unknown, verify against the Chrome Releases advisory
Fixed in
- Google Chrome 156.0.8078.47 (reported by secondary sources; later Chrome 156 builds also available, confirm against the vendor advisory)
- Microsoft Edge: reported fixed version 156.0.4314.42 (unverified, check MSRC)
- Linux distributions: follow distribution advisories (Debian DSA 6577-1, DLA 4853-1 reference this CVE; Ubuntu lists chromium-browser as not affected due to snap packaging)
Workaround
- Unknown. No vendor-documented workaround. Patching is the mitigation.
- Restart the browser after updating for the fix to take effect.
Exploitation
- No evidence of exploitation in the wild found for this CVE specifically. CISA SSVC: Exploitation none, Automatable no.
- No public proof of concept found.
- Unknown whether Google has since changed the exploitation status.
Our recommendation
- Check the Chrome version on all endpoints, including Edge and Linux packages.
- Verify that automatic updates work (Chrome enterprise policy or MSI/GPO channel).
- Deploy the newest Chrome 156 stable build and restart browsers.
- Patch within the normal high-severity window for managed fleets; not an emergency unless exploitation is confirmed.
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 issues.chromium.org
- Vulners CVE record vulners.com
- Ubuntu security notice ubuntu.com
- Vulners MSRC record (Microsoft Edge) vulners.com
- HKCERT security bulletin (Microsoft Edge) www.hkcert.org
- Cybersecurity News: Chrome 156 security update cybersecuritynews.com
- Windows Forum: Chrome 156 security update windowsforum.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, 14:04.
Original description (NVD)
Memory corruption in API 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: Medium)
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.