# CVE-2026-103626: Google Chrome FileSystem incorrect authorization in sandbox escape

Source: https://junglewise.ai/threats/cve-2026-103626-incorrect-authorization-in-filesystem-in-google-chrome-on-on  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-02. Updated: 2026-10-05  
License: CC BY 4.0 with a link back

CVE-2026-103626 · Severity: critical · CVSS 9.6 · Published 2026-10-02

Google Chrome contains an authorization flaw in its FileSystem implementation that can be exploited via a crafted HTML page shown to a user, potentially allowing an attacker to execute arbitrary code outside the browser's security sandbox. This bypasses Chrome's sandbox protection and could lead to full system compromise.

Technologies: [Google Chrome](https://junglewise.ai/threats/technologies/chrome), [Microsoft Windows](https://junglewise.ai/threats/technologies/windows). Vendors: [Google](https://junglewise.ai/threats/vendors/google), [Microsoft](https://junglewise.ai/threats/vendors/microsoft).

## Quick answers

**Is CVE-2026-103626 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-103626 being exploited in the wild.

**How severe is CVE-2026-103626?** Critical severity, with a CVSS score of 9.6, published 2 October 2026.

**Which products and versions are affected?** Google Chrome prior to 154.0.8037.97 on Windows.

**Is there a fix for CVE-2026-103626?** Yes: fixed in Chrome 154.0.8037.97. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-103626 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-103626?** Check whether you run Google Chrome or Microsoft Windows at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in Chrome 154.0.8037.97

## Technical details

An incorrect authorization check in Chrome's FileSystem component allows a remote attacker to escape the sandbox through social engineering (user interaction with a crafted HTML page). The vulnerability affects Chrome on Windows prior to version 154.0.8037.97 and enables arbitrary code execution with privileges outside the sandbox boundary.

## Affected products

- Google Chrome prior to 154.0.8037.97 on Windows

## Timeline

- 2026-10-02: disclosed

## References

- [https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop.html](https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop.html)
- [https://issues.chromium.org/issues/553114097](https://issues.chromium.org/issues/553114097)

## Related threats

- [Google Chrome out of bounds read in Skia](https://junglewise.ai/threats/cve-2026-126922-out-of-bounds-read-in-skia-in-google-chrome-prior-to-157-0-8103)
- [Google Chrome use after free in Accessibility](https://junglewise.ai/threats/cve-2026-126921-use-after-free-in-accessibility-in-google-chrome-prior-to-157-0)
- [Google Chrome information leak in Skia](https://junglewise.ai/threats/cve-2026-126920-information-leak-in-skia-in-google-chrome-prior-to-157-0-8103-78)
- [Google Chrome use-after-free in BrowserTag](https://junglewise.ai/threats/cve-2026-126919-use-after-free-in-browsertag-in-google-chrome-prior-to-157-0)
- [Google Chrome use-after-free in Layout](https://junglewise.ai/threats/cve-2026-126918-use-after-free-in-layout-in-google-chrome-prior-to-157-0-8103-78)