Google Chrome: Use-after-free in FileSystem allows sandbox code execution
Summary
A use-after-free vulnerability (CWE-416) in the FileSystem component of Google Chrome desktop allows a remote attacker to execute arbitrary code inside the browser sandbox. The attacker needs a victim to open a crafted HTML page. Full compromise would normally require a second vulnerability to escape the sandbox.
Affected
- Google Chrome desktop builds before 156.0.8078.47 (per the CVE record)
- Exact fixed builds per platform are reported inconsistently by secondary sources; verify against the vendor advisory
- Microsoft Edge: versions before 156.0.4314.42 are reported as affected (HKCERT)
- Linux distributions: Debian and Ubuntu track chromium separately; check the installed package or snap revision
Fixed in
- Chrome 156.0.8078.47 or later (Linux and Android according to secondary reports)
- Windows and macOS: 156.0.8078.47 or .48 according to secondary reports
- iOS: conflicting values reported; not verified against a primary source
- Later Chrome 156 builds also fix related FileSystem use-after-free bugs, so use the latest build
Workaround
Unknown. No vendor-recommended workaround is known; applying the update is the remedy.
Exploitation
- No evidence of exploitation in the wild found at the time of research
- No CISA KEV entry found
- No public proof-of-concept found
- CISA SSVC: exploitation none, automatable no, technical impact total
Our recommendation
- Update Chrome on all desktops to the latest Chrome 156 build and verify the version on each managed device
- Restart the browser after the update, because the old process may keep running
- Update Chromium-based browsers such as Edge and check Linux distribution packages or snaps
- Treat this as a high-priority routine update for internet-facing 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 559795243 issues.chromium.org
- Microsoft Security Update Guide: CVE-2026-113177 msrc.microsoft.com
- Ubuntu CVE tracker: CVE-2026-113177 ubuntu.com
- Vulners CVE record: CVE-2026-113177 vulners.com
- HKCERT security bulletin: Microsoft Edge multiple vulnerabilities www.hkcert.org
- Cybersecuritynews: Chrome security update fixing 353 flaws cybersecuritynews.com
- Wikipedia: Google Chrome 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, 13:17.
Original description (NVD)
Use after free 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.