Skip to main content
Mallory
HighExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2026-125350: Sandboxed Code Execution in Google Chrome XML Processing

Published Nov 10, 2026 · Updated today
Trending this week#8of 428,812 vulnerabilities
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.8High · v3.1
EPSS0.96%62nd percentile
CISA KEVYesAdded Nov 10, 2026
In the wildActivePer CISA KEV
Vendor
Google
IdentifiersCVE-2026-125350CWE-416 · Use After Free

CVE-2026-125350 is a high-severity use-after-free vulnerability in Google Chrome's XML/XSLT processing component. Processing a specially crafted HTML page can cause access to freed memory and allow a remote attacker to execute arbitrary code inside the renderer sandbox. Chrome Stable versions before 157.0.8103.50 are affected, with separate fixed versions for other release branches. Chromium-based browsers incorporating the vulnerable component may also be affected. Exploitation in the wild is confirmed, and CISA added the vulnerability to its Known Exploited Vulnerabilities catalog on November 10, 2026. Public exploitation details remain limited.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation permits arbitrary code execution with the privileges and access available to the affected sandboxed renderer process. Memory corruption may also cause browser crashes or data corruption. Data accessible to that process could be exposed or modified. This vulnerability alone does not establish sandbox escape, administrative access, or full device compromise; whether observed attacks used an additional sandbox-escape vulnerability is unknown.

Mitigation

If you can’t patch tonight, do this now.

Where patching is delayed, consider temporarily setting the XSLTEnabled enterprise policy to false in supported browsers, disabling the XSLTProcessor API and XSL processing instructions. This is an analyst-recommended workaround rather than confirmed Google guidance and should be compatibility-tested. Alternatively, use a browser confirmed to contain the fix. Maintain browser sandboxing, non-administrative execution, and supported endpoint exploit protections. Website filtering can reduce exposure but is insufficient because legitimate websites may serve compromised content.

Remediation

Patch, then assume compromise.

Install branch-appropriate browser updates and fully restart the browser, including background processes. Fixed Chrome releases include Stable 157.0.8103.50/.51 for Windows and macOS, 157.0.8103.50 for Linux and Android, Extended Stable 156.0.8078.96 for Windows and macOS, and Chrome 158 Early Stable 158.0.8127.30 for Windows. Earlier Chrome 158 builds must not be considered safe merely because their major version exceeds 157. Update other Chromium-based browsers and embedded or headless deployments using vendor-confirmed fixes; an Edge fixed-build threshold is not consistently established. Verify the running version after relaunch across managed endpoints.

Public exploits

Exploits

1 exploit validated by Mallory's analysis. Hidden: 3 rejected by Mallory's analysis as not a working exploit; 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
CVE-2026-125350-PoCThe supplied repository contains 14 files: a standalone Python delivery script, five XSLT stylesheets, four XML documents, one HTML test page, README, license, and ignore configuration. Seven files contain executable or browser-interpreted code; the four XML files provide transformation entry documents and auxiliary data. The listed file sizes total 14,347 bytes, but no archive size, repository URL, or git reference was supplied; repo.size_bytes is therefore an unknown-value placeholder of 0. poc.py uses only Python's standard library to start a threaded, loopback-bound HTTP server. Its landing page embeds import-based and union-pattern regression tests. It prefers the bundled repro/resources directory and can reconstruct all nine resource files from embedded strings. The stylesheets combine xsl:number, lazily evaluated global variables, imported templates, and document() loads to induce recursive pattern-cache evaluation. The repository attributes the resulting stale-pointer free to libxslt's xsltTestCompMatchDirect in pattern.c. This is a crash-oriented exploitation PoC, not merely passive version detection. It contains no heap grooming, controlled object reuse, RCE payload, sandbox escape, or external command-and-control traffic. External URLs in comments and documentation are references, not runtime destinations; the XSLT namespace URI is likewise not a network fetch. The script does not inspect browser state or crash dumps. Its XML counter also counts auxiliary XML requests and may count unsuccessful requests, so it is not an exploitation-success metric. A delivery caveat is that assigning Handler.directory at class level does not pass a directory argument to SimpleHTTPRequestHandler; normal initialization uses the current working directory. Combined with the /repro path rewrite, this makes serving dependent on launching from the repository root. The README describes vulnerable browser backups and crash dumps, but neither is included in the supplied files. The claimed CVE assignment, official regression-test provenance, affected versions, and reproduction results were not independently verified.TJT001 · Disclosed Nov 11, 2026 · python · xslt · browserPoC
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GoogleChromeapplication
FAQ

Frequently asked questions

Is CVE-2026-125350 exploited in the wild?
Yes. As of Nov 17, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Nov 10, 2026.
Is there a public exploit for CVE-2026-125350?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2026-125350, the earliest disclosed Nov 11, 2026.
Is there a patch for CVE-2026-125350?
Install branch-appropriate browser updates and fully restart the browser, including background processes. Fixed Chrome releases include Stable 157.0.8103.50/.51 for Windows and macOS, 157.0.8103.50 for Linux and Android, Extended Stable 156.0.8078.96 for Windows and macOS, and Chrome 158 Early Stable 158.0.8127.30 for Windows.
What products are affected by CVE-2026-125350?
Google Chrome.
How severe is CVE-2026-125350?
CVE-2026-125350 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 0.96% (62nd percentile) as of Nov 17, 2026.
Activity feed

Recent activity

227 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

View more in app →

No news coverage yet. Advisories and community discussion only.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signatures2YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.