Quick answers
- Is CVE-2026-120930 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-120930 being exploited in the wild.
- How severe is CVE-2026-120930?
- Informational severity, published 3 November 2026.
- Which products and versions are affected?
- Google Chrome prior to 156.0.8078.47.
- Is there a fix for CVE-2026-120930?
- Yes: fixed in Chrome 156.0.8078.47 and later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-120930 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-120930?
- Check whether you run Google Chrome 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 156.0.8078.47 and later
Technical details
An incorrect authorization check in the Blink component of Chrome prior to 156.0.8078.47 permits remote attackers to bypass same-origin policy (SOP) via a crafted HTML page delivered over the network. The vulnerability requires user interaction (visiting a malicious page) but does not require authentication. Successful exploitation allows JavaScript code to access resources and data from different origins than the page's declared origin.
Affected products
- Google Chrome prior to 156.0.8078.47
Timeline
- 2026-05-23: disclosed: Reported by lebr0nli of National Yang Ming Chiao Tung University, Dept. of CS, Security and Systems Lab
- 2026-10-20: patched: Fixed in Chrome 156.0.8078.47 stable release