Google Chrome: Memory corruption in FileSystem allows code execution in sandbox
Summary
Google Chrome for desktop contains a memory corruption flaw (CWE-119) in its FileSystem component. A remote attacker can use a crafted HTML page to execute arbitrary code inside the browser sandbox. The attack requires that a user visits the malicious page, for example through a phishing link or a malicious advertisement. Chromium rates the issue Medium, while NVD scores it 8.8 (High).
Affected
- Google Chrome desktop builds before 156.0.8078.47
Fixed in
- Linux: 156.0.8078.47
- Windows and macOS: 156.0.8078.48 or later (secondary sources list .47 and .48; use .48 or later to be safe)
Workaround
No workaround is needed. Updating is the mitigation. Relaunch the browser after updating.
Exploitation
- No known exploitation in the wild according to the sources reviewed. Google has not stated otherwise.
- Not listed in CISA KEV.
- No public proof of concept found; this does not prove that none exists.
Our recommendation
- Update all desktop Chrome installations to 156.0.8078.48 or later on Windows and macOS, or 156.0.8078.47 or later on Linux.
- Relaunch Chrome after the update, because an old browser process may still be running.
- Verify the installed version instead of assuming the update has been applied.
- Check other Chromium-based browsers such as Microsoft Edge and Chromium packages for their own updates.
- Use your management tooling to confirm the rollout across all endpoints.
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
- Chrome 156 security update (CyberSecurityNews) cybersecuritynews.com
- Ubuntu security tracker ubuntu.com
- Debian and Fedora advisories via Vulners vulners.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:46.
Original description (NVD)
Memory corruption in FileSystem 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.