Google Chrome: Memory corruption in Loader allows code execution in sandbox
Summary
Google Chrome contains a memory corruption flaw in its Loader component. A remote attacker can execute arbitrary code inside the browser sandbox by luring a user to a crafted HTML page. The CVE record does not describe a sandbox escape, so full system compromise would require an additional vulnerability. NVD rates the issue CVSS 8.8, while Chromium rates it Low.
Affected
- Google Chrome builds prior to 156.0.8078.47
Per-platform build numbers conflict between sources. Check the vendor advisory.
Fixed in
- Google Chrome 156.0.8078.47 (first fixed build according to the CVE text)
- Per-platform mapping unconfirmed: secondary sources list 156.0.8078.48 for Windows and Mac.
- Later Chrome 156 stable builds exist. Install the newest Chrome 156 stable build.
- Chromium-based products such as Microsoft Edge and Linux distribution packages need their own updates.
Workaround
Unknown. No browser-side workaround is documented. Enforce automatic updates or use Chrome Enterprise policies to deploy and verify the version.
Exploitation
- CISA KEV: not listed.
- EPSS: 0.42%.
- Public proof of concept: none found. Status unknown.
- In the wild: no evidence found. The Chromium issue tracker could not be verified.
- CISA SSVC: exploitation none, automatable no, technical impact total.
Our recommendation
- Verify that all endpoints run the latest Chrome 156 stable build or later.
- Enforce automatic updates and monitor update compliance centrally.
- Check Chromium-based browsers (for example Microsoft Edge) and Linux packages separately.
- Prioritise endpoints with unmanaged or outdated browsers, because the attack requires only that a user opens a crafted page.
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
- NVD record via Vulners vulners.com
- Debian CVE list via Vulners vulners.com
- Microsoft CVE entry via Vulners vulners.com
- Ubuntu security notice ubuntu.com
- VulDB entry vuldb.com
- Google Chrome (Wikipedia) en.wikipedia.org
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, 15:04.
Original description (NVD)
Memory corruption in Loader 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.