Google Chrome: Use after free in FileSystem allows code execution
Summary
A use-after-free flaw in the FileSystem component of Google Chrome before 155.0.8059.79 allows a remote attacker to execute arbitrary code outside the browser sandbox. The attacker only needs to lure a user to a crafted HTML page, so any website, including a compromised legitimate site or a malicious ad, can be the attack vector. NVD scores the issue 9.6 (Critical), while Chromium rates it Medium, and the CVSS vector assumes a sandbox escape that the record does not detail.
Affected
- Google Chrome prior to 155.0.8059.79 (desktop and Android, per vendor release notes)
- Debian package chromium: prior to 155.0.8059.79-1~deb12u1
- Ubuntu: chromium-browser is marked not affected because it installs a Snap; the Snap must be updated separately
Fixed in
- Google Chrome 155.0.8059.79 or later (Stable channel update of 13 October 2026)
- Chrome 156 is newer and should be used as the current target
- Debian: 155.0.8059.79-1~deb12u1
Workaround
- No mitigation published for this CVE.
- Until patching is complete, limit browsing to trusted sites.
- Restart Chrome after the update, because the fix is only active after a relaunch.
Exploitation
- CISA SSVC: exploitation none, automatable no, technical impact total.
- No evidence of in-the-wild exploitation found; one secondary report says Google's post lists no attacks in the wild (not confirmed from Google's post).
- Not listed in the CISA KEV catalog per a tracker snapshot; recheck the catalog.
- No public proof of concept found.
Our recommendation
- Update all desktop and Android Chrome installations to the current Stable build as a priority.
- Verify that Chrome has actually restarted after the update.
- Check that managed browsers receive the update and that Snap-based Chromium installs are updated.
- Keep browser updates on a short cycle and monitor the CISA KEV catalog for changes.
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
- OSV: DEBIAN-CVE-2026-110142 osv.dev
- Ubuntu Security: CVE-2026-110142 ubuntu.com
- Malwarebytes: Chrome 155 fixes 37 security flaws www.malwarebytes.com
- Strix: CVE-2026-110142 www.strix.ai
- SUSE CVE via Vulners: CVE-2026-110142 vulners.com
- GitHub CVE tracker issue 1955 github.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 30 Oct 2026, 22:54.
Original description (NVD)
Use after free in FileSystem in Google Chrome prior to 155.0.8059.79 allowed a remote attacker to execute arbitrary code outside 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.