Quick answers
- Is CVE-2026-126907 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-126907 being exploited in the wild.
- How severe is CVE-2026-126907?
- 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-126907?
- Yes: fixed in 157.0.8103.78, 157.0.8103.79. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-126907 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-126907?
- 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: 157.0.8103.78, 157.0.8103.79
Technical details
An uninitialized resource in Chrome's Media component fails to properly initialize memory before use, allowing an attacker who has already compromised the renderer process to read memory outside the sandbox via a crafted HTML page. This requires prior renderer compromise but enables sandbox escape and arbitrary memory disclosure. The vulnerability is fixed in Chrome 157.0.8103.78 and later.
Affected products
- Google Chrome prior to 157.0.8103.78
Timeline
- 2026-11-11: disclosed
- 2026-11-11: patched