Quick answers
- Is CVE-2026-126900 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-126900 being exploited in the wild.
- How severe is CVE-2026-126900?
- 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-126900?
- Yes: fixed in Chrome 157.0.8103.78 for Linux, 157.0.8103.78/.79 for Windows and Mac. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-126900 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-126900?
- 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 for Linux, 157.0.8103.78/.79 for Windows and Mac
Technical details
A use-after-free vulnerability exists in the CSS component of Google Chrome prior to version 157.0.8103.78/79. The vulnerability can be exploited remotely via a crafted HTML page, allowing code execution within the browser's sandbox. The fix was applied in Chrome 157.0.8103.78 for Linux and 157.0.8103.78/.79 for Windows and Mac.
Affected products
- Google Chrome prior to 157.0.8103.78
Timeline
- 2026-11-11: disclosed
- 2026-10-16: other: Vulnerability reported to Google