Google Chrome: Incorrect authorization in FileSystem allows sandbox escape
Summary
A flaw in the FileSystem component of Google Chrome allows incorrect authorization. A remote attacker who tricks a user into opening a crafted HTML page can execute arbitrary code outside the browser sandbox. The attack needs user interaction and social engineering, but no authentication. Google rates the issue High, and the CVSS score of 9.6 given in the CVE data could not be confirmed.
Affected
- Google Chrome desktop prior to 157.0.8103.50 (per the CVE description)
- The CVE record's affected range is internally inconsistent ("157.0.8103.50 to < 157.0.8103.50"), so the description is the basis here
Fixed in
- Linux and Android: 157.0.8103.50 (per press coverage)
- Windows and macOS: 157.0.8103.50/.51 (per press coverage)
- Extended Stable: unknown; the separate 156.0.8078.96 build for Windows and macOS could not be confirmed to contain this fix
- ChromeOS: no Stable update listing this fix had been published at the time of research
Workaround
Unknown. No workaround is documented; the only mitigation is to install the browser update.
Exploitation
- CISA SSVC: Exploitation none, Automatable no, Technical Impact total
- No known exploitation of this CVE as of 10 Nov 2026 (third-party snapshot), and no public proof of concept found
- CVE-2026-125350 (XML use-after-free) is a different flaw in the same release that is known to be exploited in the wild
Our recommendation
- Update Chrome to 157.0.8103.50 or later (Linux, Android) or 157.0.8103.50/.51 or later (Windows, macOS) on all endpoints, and verify the version at chrome://version
- Deploy the update through managed deployment and confirm that browsers are restarted
- Check Extended Stable installations separately
- Check Microsoft Edge, Brave and other Chromium-based browsers for their own security updates
- Monitor the Chromium issue and NVD for changes to the exploitation status or CVSS score
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
- CVE record (threatint) cve.threatint.com
- OffSeq radar: CVE-2026-125347 radar.offseq.com
- Strix: CVE-2026-125347 www.strix.ai
- Malware.news: Update Chrome now to fix a flaw attackers are exploiting malware.news
- The Register: Chrome zero-day whack-a-mole continues www.theregister.com
- ChromeGeek: Chrome zero-day CVE-2026-125350 www.chromegeek.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 10 Nov 2026, 22:22.
Original description (NVD)
Incorrect authorization in FileSystem in Google Chrome prior to 157.0.8103.50 allowed a remote attacker leveraging social engineering to execute arbitrary code outside 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.