Google Chrome Zero-Day Use-After-Free in XML Actively Exploited

Red | Vulnerability
Google Chrome Zero-Day Use-After-Free in XML Actively Exploited | Hive Pro Threat Advisory
Date of publication
November 10, 2026
Last update date
November 11, 2026
Admiralty code
A1
TA number
TA2026331
First seen
November 09, 2026
Affected products
Google Chrome (Windows and Mac prior to 157.0.8103.50/.51; Linux prior to 157.0.8103.50; Extended Stable for Windows and Mac prior to 156.0.8078.96)

Summary

Google has patched CVE-2026-125350, a High-severity use-after-free vulnerability in Chrome's XML component that is being actively exploited in the wild, with the fix shipped in Stable 157.0.8103.50/.51 for Windows and macOS and 157.0.8103.50 for Linux on November 9, 2026, and in Extended Stable 156.0.8078.96 for Windows and Mac. Reported by an anonymous researcher on November 6 and the eighth exploited Chrome zero-day of 2026, the flaw lets a remote attacker corrupt memory through crafted web content when Chrome's XML component continues to use an object after it has been freed.

Google has withheld attack details pending broad patch adoption, and no threat actor or targeting has been attributed. Organisations should update Chrome immediately and track fixes for other Chromium-based browsers, which share the vulnerable XML code.

CVENameAffected product
CVE-2026-125350Google Chrome Use-After-Free in XML VulnerabilityGoogle Chrome

Vulnerability Details

#1

Google has shipped Chrome 157.0.8103.50/.51 for Windows and Mac and 157.0.8103.50 for Linux to the Stable channel, released November 9, 2026, with the rollout continuing over the coming days and weeks. The Extended Stable channel received the same fix in 156.0.8078.96 for Windows and Mac. The build fixes nine vulnerabilities, CVE-2026-125342 through CVE-2026-125350, and Google has confirmed that an exploit for CVE-2026-125350 exists in the wild.

#2

CVE-2026-125350 is a use-after-free flaw (CWE-416) in Chrome's XML handling that a remote attacker can exploit. Use-after-free bugs occur when memory is referenced after it has been freed, and in a browser they can typically be triggered by attacker-controlled web content to corrupt memory. Possible outcomes of the vulnerabilities in this release include remote code execution, denial of service and security restriction bypass.

#3

Google has confirmed the flaw sits in Chrome's XML component but has not published technical details, the exploitation method or indicators of compromise. Organisations should update Chrome immediately rather than wait for the staged rollout, and track other Chromium-based products that may share the vulnerable code.

Affected products, CPE and CWE
CVE IDAffected productsAffected CPECWE ID
CVE-2026-125350Google Chrome (Before 157.0.8103.50/.51 on Windows and Mac; Before 157.0.8103.50 on Linux; Extended Stable before 156.0.8078.96 on Windows and Mac)cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*CWE-416

Recommendations

  1. 01

    Update Chrome Immediately

    Upgrade all Chrome installations to 157.0.8103.50/.51 or later on Windows and Mac and 157.0.8103.50 or later on Linux; managed fleets on the Extended Stable channel need 156.0.8078.96 or later on Windows and Mac. Users can force the update via More > Help > About Google Chrome and then Relaunch; enterprises should push the build through their management tooling rather than waiting for the staged rollout.

  2. 02

    Patch Chromium-Based Browsers as Fixes Land

    Other Chromium-based browsers and applications that embed Chromium components may inherit the flaw. Track each vendor's release channel and apply the corresponding update as soon as it is published.

  3. 03

    Hunt for Exploitation Indicators

    Because CVE-2026-125350 is confirmed as exploited in the wild but attack details are not yet public, review browser process telemetry for anomalous renderer crashes, unexpected child processes spawned by the browser, and suspicious outbound connections following visits to untrusted websites.

  4. 04

    Reduce Exposure Until Patched

    Where immediate patching is not possible, restrict browsing to trusted destinations through web filtering, keep site isolation and sandbox protections enabled, and apply stricter browsing policies for high-value users such as administrators and executives.

  5. 05

    Enforce Browser Update Policy

    Configure Chrome enterprise policies to disallow update deferral and to relaunch within a defined window after an update is staged, so that future actively exploited flaws are closed quickly across the estate.


Potential MITRE ATT&CK TTPs

Initial Access
T1189Drive-by Compromise
Execution
T1203Exploitation for Client Execution
Stealth
T1211Exploitation for Stealth
Defense Impairment
T1687Exploitation for Defense Impairment
Impact
T1499Endpoint Denial of Service
T1499.004Application or System Exploitation

References & Patch Links

Patch link
References

What Next?

At Hive Pro, it is our mission to detect the most likely threats to your organization and to help you prevent them from happening.

Reduce real exposure. Not just vulnerability volume.