Is CVE-2026-126913 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-126913 being exploited in the wild.

How severe is CVE-2026-126913?

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-126913?

Yes: fixed in Chrome 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-126913 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-126913?

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.

CVE-2026-126913: Google Chrome out-of-bounds read in Compositing

CVE-2026-126913 · Severity: info · Published 2026-11-11

Google Chrome is a web browser used by billions of people worldwide. A flaw in Chrome's compositing engine allows an attacker who has already compromised the browser's rendering process to read sensitive memory outside the security sandbox, potentially exposing user data. This requires the attacker to first compromise the renderer, typically through a separate browser vulnerability.

Technologies: Google Chrome. Vendors: Google.

Quick answers

Is CVE-2026-126913 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-126913 being exploited in the wild.
How severe is CVE-2026-126913?: 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-126913?: Yes: fixed in Chrome 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-126913 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-126913?: 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, 157.0.8103.79

Technical details

An out-of-bounds read vulnerability exists in Chrome's Compositing component (CVE-2026-126913), affecting versions prior to 157.0.8103.78. The vulnerability requires a compromised renderer process and a crafted HTML page to trigger; it allows reading memory beyond allocated boundaries, bypassing the renderer sandbox. The fix is available in Chrome 157.0.8103.78 and later.

Affected products

Google Chrome prior to 157.0.8103.78

Timeline

2026-11-11: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.