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