Is CVE-2026-126919 exploited in the wild?

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

How severe is CVE-2026-126919?

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

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-126919 attacked?

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

Am I affected by CVE-2026-126919?

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-126919: Google Chrome use-after-free in BrowserTag

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

Google Chrome is a web browser used by billions of people to access websites and web applications. A use-after-free flaw in the BrowserTag component allows attackers to execute arbitrary code within Chrome's sandbox by sending a crafted web page, potentially leading to full compromise of the browsing session and theft of sensitive data.

Technologies: Google Chrome. Vendors: Google.

Quick answers

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

A use-after-free vulnerability exists in Chrome's BrowserTag component, allowing remote code execution within the renderer sandbox via a malicious HTML page. The vulnerability requires user interaction (visiting a malicious site) but no prior authentication. An attacker can gain code execution within the sandbox environment.

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.