CVE-2026-125350 - Google Chromium Use-After-Free Vulnerability

CVE-2026-125350

Chrome 157 - Re-Entrant XSLT Pattern Cache Use-After-Free, Eighth Exploited Zero-Day of 2026

What is Chromium?

Chromium is the open-source browser engine Google maintains and builds Chrome from. It is also the base for Microsoft Edge, Opera, Brave, Vivaldi, Samsung Internet, and the Electron runtime that powers desktop applications such as Slack, Teams, Discord, and VS Code. A memory corruption bug in Chromium therefore does not stay in Chrome; it propagates to every downstream browser and to a large amount of software most users would not describe as a browser at all.

The component at issue here is XSLT support, supplied by the bundled libxslt library. XSLT is a stylesheet language that transforms XML documents into other formats, and browsers have supported it since the early 2000s. It is rarely used on the modern web but it is enabled by default, it parses complex attacker-controlled input, and it is written in C. That combination, legacy surface, default-on, memory-unsafe, is why it keeps producing exploited zero-days.

Overview

CVE-2026-125350 is a use-after-free in Chrome's XML handling, specifically in the direct pattern match cache inside libxslt. Google rates it High and shipped the fix in Chrome 157.0.8103.50 and .51 on 2026-11-09, stating that it is aware an exploit for the flaw exists in the wild. NVD scores it 8.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H).

The exploitation window was short and the response was fast. An anonymous researcher reported the bug on 2026-11-06, the fix landed in Chromium on 2026-11-07, and the stable build shipped on 2026-11-09, three days from report to release. CISA published the KEV entry on 2026-11-10 with a BOD 26-04 deadline of 2026-11-24. This is the eighth Chrome zero-day found exploited in attacks during 2026.

The same release closed nine security bugs in total, seven of them High. Among them is CVE-2026-125346, a second use-after-free in the XML component reported by Arni Hardarson of Neonix Security on 2026-10-12. Google has not said that one is exploited, but it is fixed by the same update, so there is no reason to treat the two separately when patching.

Affected Versions

Product Vulnerable Fixed
Google Chrome, Windows and macOS Earlier than 157.0.8103.50 157.0.8103.50 or 157.0.8103.51
Google Chrome, Linux Earlier than 157.0.8103.50 157.0.8103.50
Google Chrome, Extended Stable Earlier than 156.0.8078.96 156.0.8078.96
Microsoft Edge, Opera, Brave, Vivaldi and other Chromium browsers Builds on an unpatched Chromium base Each vendor's own update carrying the fix
Other software embedding libxslt Potentially affected Check with the vendor; the Chromium fix had not been taken upstream at the time of writing

Technical Details

The flaw is CWE-416, use after free: the program keeps using a pointer to memory it has already released. In this case the stale pointer lives in the direct pattern match cache used by xsltTestCompMatchDirect() in libxslt/pattern.c.

The sequence is a re-entrancy problem. The function reads a cached node-set pointer, then calls xmlXPathEval() to evaluate an expression. XSLT allows lazy evaluation, so that evaluation can re-enter the very same function for the very same cache slot. A lazily evaluated global variable that invokes xsl:number, for example, can free or replace the cached object while the outer call is still holding its original pointer. When the outer call returns and releases what it believes it owns, the result is a double free, and the cache is left pointing at memory that has been handed back to the allocator. The published fix re-reads the cache slot after evaluation rather than trusting the pointer it captured before, and landed as Chromium commit 61cab3f77203.

Reaching the bug needs no privileges and no interaction beyond loading a page: a victim opens content that pulls in attacker-controlled XML with an XSLT stylesheet, a template match or xsl:number pattern primes the cache, and the re-entrant call corrupts it. That is why the CVSS vector carries UI:R but AC:L and PR:N. Importantly, the corruption happens in the renderer process, which is sandboxed. Turning this into code execution on the host requires chaining it with a sandbox escape. Google has not said whether the in-the-wild exploit includes one.

Discovery

Google credits the report to an anonymous researcher who submitted it on 2026-11-06. Reports of actively exploited browser bugs are frequently anonymized when they come from a party that does not want the submission tied to them, whether a commercial surveillance-vendor tracker, a government team, or an incident responder who recovered the exploit from a victim machine, so the anonymity is itself a mild signal that this was found in use rather than found by fuzzing.

The companion XML use-after-free in the same release, CVE-2026-125346, carries a named credit: Arni Hardarson of Neonix Security, reported 2026-10-12. Google has withheld bug details and the Chromium bug tracker entry, as it normally does until a majority of users have updated, so no exploit sample, victim set, or indicator of compromise is public.

Exploitation Context

Google's statement, that it is aware an exploit exists in the wild, is the full extent of confirmed exploitation detail. There is no named threat actor, no targeting information, no victim count, and no published indicators of compromise. CISA's KEV entry does not flag known ransomware use.

What can be said is contextual. Historically, exploited Chrome zero-days in the rendering and scripting layers have skewed toward targeted intrusion and commercial spyware delivery rather than mass exploitation, and the renderer sandbox means this bug alone does not yield host compromise. The realistic attack is a watering hole or a targeted link, combined with a second bug to escape the sandbox.

The downstream surface is the part most organizations underestimate. Microsoft Edge, Opera, Brave, and Vivaldi each ship their own rebuilt Chromium and release on their own schedule, so there is a lag of days between the Chrome fix and the fix reaching those users. Electron applications lag further, sometimes by weeks, and they are rarely covered by browser patch policies.

Remediation

  1. Update Chrome to 157.0.8103.50 or later on Windows, macOS, and Linux, or 156.0.8078.96 on the Extended Stable channel. Chrome downloads updates automatically but does not apply them until the browser is restarted, so a restart is part of the fix, not an optional follow-up.
  2. Verify deployment rather than assuming it. Check chrome://settings/help on a sample of machines, or report on browser version through your endpoint management tooling, and chase the long tail of machines that never get closed.
  3. Update every other Chromium-based browser in the estate as its vendor ships the fix: Edge, Opera, Brave, Vivaldi, and Samsung Internet each need their own update. Treat Chrome being patched as covering Chrome only.
  4. Inventory Electron applications and other embedders of Chromium or libxslt, and apply their updates when available. The Chromium patch had not been adopted upstream in libxslt at the time of writing, so independent software embedding that library may still be vulnerable.
  5. There is no configuration switch that disables the vulnerable code while keeping XSLT working. Blocking untrusted XML and XSLT content at a proxy reduces exposure but is not a fix and should not be treated as one.
  6. For high-risk users, review browser history and proxy logs for unexpected XML or XSLT content loads, and preserve the relevant logs before remediating, in line with CISA's Forensics Triage Requirements under BOD 26-04. No indicators of compromise have been published, so this is best-effort hunting rather than a defined search.
  7. Federal civilian agencies must remediate by 2026-11-24. Given that an exploit is already in use and a browser restart is the entire remediation for most endpoints, there is no reason to use the full window.

Key Details

PropertyValue
CVE ID CVE-2026-125350
Vendor / Product Google - Chromium
NVD Published2026-11-10
NVD Last Modified2026-11-10
CVSS 3.1 Score8.8
CVSS 3.1 VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
SeverityHIGH
CWE CWE-416 find similar ↗
CISA KEV Added2026-11-10
CISA KEV Deadline2026-11-24
Known Ransomware Use No

CVSS 3.1 Breakdown

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Required Action

CISA BOD 26-04 Deadline: 2026-11-24. Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA's BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA's "Forensics Triage Requirements" (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

Timeline

DateEvent
2026-11-06An anonymous researcher reports the use-after-free to Google
2026-11-07Fix lands in Chromium (commit 61cab3f77203), re-reading the pattern cache slot after evaluation
2026-11-09Chrome 157.0.8103.50/.51 released to the stable desktop channel; Google states an exploit exists in the wild
2026-11-10CVE published and added to the CISA Known Exploited Vulnerabilities catalog
2026-11-24CISA BOD 26-04 remediation deadline