Google Chrome: Improper input validation in FileSystem enables sandbox code execution
Summary
Improper input validation in the FileSystem component of Google Chrome before 156.0.8078.47 allows a remote attacker to execute arbitrary code inside the browser sandbox. The attacker must lure a user to a crafted HTML page, so user interaction is required. The vendor describes the impact as code execution inside the sandbox, not as a confirmed sandbox escape. The CNA rates the issue High (CVSS 3.1: 8.8), while VulDB scores it 6.3 (Medium).
Affected
- Google Chrome (desktop and Android) prior to 156.0.8078.47
- VulDB's title lists up to 155.0.8059.84; the CVE text is authoritative
- iOS: affected version range unverified
Fixed in
- Linux and Android: 156.0.8078.47
- Windows and macOS: 156.0.8078.47 or 156.0.8078.48
- iOS: fixed build unverified (sources conflict)
- Later 156.x builds also exist and are recommended
Workaround
Unknown. No vendor workaround found; the update is the fix.
- Until updated, restrict browsing to trusted sites (general measure, not vendor-recommended)
Exploitation
- No evidence of exploitation in the wild found; Strix lists it as not in KEV
- No public proof-of-concept found
- Google's bug entry is restricted; exploit details are not disclosed
Our recommendation
- Verify that all managed Chrome installations run 156.0.8078.47 or later (156.0.8078.48 on Windows and macOS), preferably the latest 156.x build
- Restart the browser after updating, as the update takes effect only then
- Check Android, iOS and Chromebook fleets separately
- Ubuntu users: check the installed chromium snap revision instead of relying on the 'not affected' status
Public exploits
PoC-in-GitHub, Metasploit and Exploit-DB list nothing for this CVE.
Research sources
- Google Chrome Releases: Stable Channel Update for Desktop chromereleases.googleblog.com
- Chromium issue tracker entry issues.chromium.org
- Ubuntu security tracker: CVE-2026-113175 ubuntu.com
- VulDB entry vuldb.com
- Vulners CNNVD record vulners.com
- Windows Forum: Chrome 156 security update windowsforum.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, 13:16.
Original description (NVD)
Improper input validation 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: High)
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.