Google Chrome: Memory corruption in Core allows code execution in sandbox
Summary
A memory corruption flaw in the Core component of Google Chrome before 156.0.8078.47 allows a remote attacker to execute arbitrary code inside the browser sandbox via a crafted HTML page. The victim must open the page, for example through a phishing link or a malicious website. Chromium rates the issue Low, while NVD scores it 8.8 (High). No evidence of exploitation in the wild or public proof of concept was found.
Affected
- Google Chrome prior to 156.0.8078.47 (per CVE description)
- Note: the official CVE record's version range is internally inconsistent (156.0.8078.47 to less than 156.0.8078.47); verify against the vendor advisory.
- Chromium-based browsers such as Microsoft Edge need their own updates.
Fixed in
- Google Chrome 156.0.8078.47 (Linux) or later
- Google Chrome 156.0.8078.47/.48 (Windows and macOS) or later
- Newer 156.x builds exist (reported as 156.0.8078.79/.80); verify against the Chrome Releases blog.
- Debian: DSA 6577-1 and DLA 4853-1 for Chromium.
Workaround
- No vendor-documented workaround is known beyond updating.
- Chrome applies updates only after a browser restart, so browsers left open for days may remain vulnerable.
Exploitation
- No evidence of exploitation in the wild found; CISA KEV status not directly verified.
- No public proof of concept found.
- CISA SSVC: exploitation none, automatable no, technical impact total.
Our recommendation
- Inventory all Chrome, Edge and Chromium installations and confirm they run 156.0.8078.47/.48 or later, preferably the newest 156.x build.
- Force a browser restart on managed endpoints and enforce updates via MDM or GPO.
- Patch Linux Chromium packages per distribution advisories and check snap-based installations.
- Monitor for KEV entries or public exploit code.
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
- HKCERT security bulletin www.hkcert.org
- NVD record via Vulners vulners.com
- Debian CVE list entry via Vulners vulners.com
- Ubuntu security tracker ubuntu.com
- VulDB entry vuldb.com
- Strix CVE entry www.strix.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, 12:18.
Original description (NVD)
Memory corruption in Core 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: Low)
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.