Quick answers
- Is CVE-2026-126918 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-126918 being exploited in the wild.
- How severe is CVE-2026-126918?
- 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-126918?
- Yes: fixed in Chrome 157.0.8103.78 (Windows, 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-126918 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-126918?
- 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), 157.0.8103.78 (Linux)
Technical details
A use-after-free vulnerability exists in the Layout rendering component of Google Chrome prior to version 157.0.8103.78. An attacker can trigger the vulnerability by crafting a malicious HTML page and causing a user to visit it; the memory corruption allows arbitrary code execution within the browser sandbox. This is a memory safety issue in a core rendering component.
Affected products
- Google Chrome prior to 157.0.8103.78
Timeline
- 2026-11-11: disclosed
- 2026-11-11: patched