Quick answers
- Is CVE-2026-126917 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-126917 being exploited in the wild.
- How severe is CVE-2026-126917?
- 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-126917?
- Yes: fixed in Chrome 157.0.8103.78 (Windows and Mac), 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-126917 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-126917?
- 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 and Mac), 157.0.8103.78 (Linux)
Technical details
A memory corruption flaw exists in Chrome's V8 JavaScript engine that can be exploited remotely via a crafted HTML page. The vulnerability allows an attacker to escape the sandbox and achieve arbitrary code execution. The attack requires only network access and user interaction (visiting a malicious webpage).
Affected products
- Google Chrome prior to 157.0.8103.78
Timeline
- 2026-11-11: disclosed
- 2026-11-11: patched