Quick answers
- Is CVE-2026-126905 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-126905 being exploited in the wild.
- How severe is CVE-2026-126905?
- Informational severity, published 11 November 2026.
- Which products and versions are affected?
- Google Chrome prior to 157.0.8103.78.
- Is there a fix for CVE-2026-126905?
- Yes: fixed in Chrome 157.0.8103.78 (Windows, Mac) and 157.0.8103.78 (Linux). Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-126905 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-126905?
- 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 157.0.8103.78 (Windows, Mac) and 157.0.8103.78 (Linux)
Technical details
Incomplete cleanup in V8's memory management allows a remote attacker to potentially execute arbitrary code within the sandbox via a crafted HTML page. The vulnerability requires only that a user visit a malicious website; no authentication or additional user interaction beyond normal browsing is needed. Exploitation leads to code execution within Chrome's sandbox, which provides some containment but could be chained with other vulnerabilities for full system compromise.
Affected products
- Google Chrome prior to 157.0.8103.78
Timeline
- 2026-11-11: disclosed