Google Chrome: Memory corruption in SiteIsolation allows sandbox code execution
Summary
Google Chrome prior to 156.0.8078.47 contains a memory corruption flaw (CWE-119) in SiteIsolation, Chrome's process-separation mechanism for web content. A remote attacker can use a crafted HTML page to potentially execute arbitrary code inside the browser sandbox. Exploitation requires that a user opens the malicious page; the code execution described is confined to the sandbox, so a full compromise would normally need a second flaw. NVD rates the issue 8.8 (High), while Chromium rates it Medium.
Affected
- Google Chrome prior to 156.0.8078.47 (NVD description)
- Vendor range wording is inconsistent across third-party sources; NVD wording is used here.
Fixed in
- Google Chrome 156.0.8078.47 and later (Windows, Mac, Linux), per the Chrome Releases post of 20 October 2026
- Newer stable builds exist; the current version should be checked on the official Chrome Releases blog.
- Debian chromium packages (DSA 6577-1, DLA 4853-1) reference this CVE; exact fixed package versions are unknown.
- Ubuntu lists its chromium-browser packages as not affected because they install the Snap.
Workaround
- None needed if patched.
- No workaround was found in the sources. Unknown whether any setting or feature flag mitigates this bug.
Exploitation
- No evidence of in-the-wild exploitation found.
- No public proof of concept found.
- CISA SSVC: Exploitation none, Automatable no, Technical Impact total.
Our recommendation
- Update Google Chrome to the current stable release on all Windows, Mac and Linux endpoints, using managed updates.
- Verify the Chrome version on all endpoints, including Chromium-based browsers that consume these fixes.
- Enforce a minimum Chrome version through Chrome Enterprise policy or your endpoint management tool.
- Prioritise this update, since drive-by delivery through web pages requires no credentials.
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 mirror on Vulners vulners.com
- HKCERT security bulletin www.hkcert.org
- Ubuntu security notice ubuntu.com
- Strix CVE page 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, 13:35.
Original description (NVD)
Memory corruption in SiteIsolation in Google Chrome prior to 156.0.8078.47 allowed a remote attacker to potentially 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.