
Proof-of-concept trigger and detection notes for CVE-2026-125350, a use-after-free in Chrome's XML parser (CVSS 8.8, Chrome < 157.0.8103.50, CISA KEV).
A use-after-free (UAF) vulnerability in Google Chrome's XML parser allows a remote attacker to execute arbitrary code inside the renderer sandbox via a crafted HTML page. Google confirmed active exploitation in the wild before the patch and added the CVE to CISA's KEV catalog on November 10, 2026. This is the eighth Chrome zero-day patched in 2026.
| Field | Value |
|---|---|
| CVE | CVE-2026-125350 |
| CVSS 3.1 | 8.8 High — AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| CWE | CWE-416 (Use After Free) |
| Component | Chrome XML parser (Blink/libxml2 integration) |
| Affected | Google Chrome < 157.0.8103.50 |
| Fixed | Chrome 157.0.8103.50 / 157.0.8103.51 (2026-11-09) |
| KEV | CISA added 2026-11-10, federal deadline 2026-11-24 |
| Auth Required | None — victim visits a crafted page |
| Disclosed | 2026-11-09 |
Chrome's XML component frees a node object during document parsing but does not clear all references to the freed memory before the memory region can be reused. A crafted HTML page can trigger the free and then access the dangling pointer, achieving controlled memory corruption inside the renderer process.
The impact is bounded by the Chrome renderer sandbox — an attacker gains code execution inside the sandbox and would need a separate sandbox escape to fully compromise the system.
flowchart LR
A([Attacker\nMalicious page]) -->|Victim visits URL\nor opens crafted HTML| B[Chrome Renderer\n< 157.0.8103.50]
B -->|XML parse triggers\nnode free| C[Freed object\nstill referenced]
C -->|Reallocation\ncontrolled data| D[UAF read/write\nin renderer heap]
D -->|Arbitrary code\ninside sandbox| E([Renderer RCE\nin sandbox])
E -.->|+ sandbox escape\nfor full OS access| F[Full compromise]
style A fill:#3d1a1a,stroke:#f85149,color:#f85149
style E fill:#1a1f2e,stroke:#f85149,color:#f85149
style F fill:#1a1f2e,stroke:#a855f7,color:#a855f7
Warning: Lab environment only. The trigger HTML requires Chrome < 157.0.8103.50. Use an isolated VM — do not run on production systems.
# No Python dependencies — PoC is a self-contained HTML page
# Serve with any HTTP server on the attacker machine:
python3 -m http.server 8080
# Then open trigger.html in a vulnerable Chrome instance
# Linux
google-chrome --version
# macOS
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version
# Windows (PowerShell)
(Get-Item "C:\Program Files\Google\Chrome\Application\chrome.exe").VersionInfo.ProductVersion
# Serve the PoC
python3 poc.py --mode serve --port 8080
# Or generate the trigger HTML only
python3 poc.py --mode craft --out trigger.html
Then open in vulnerable Chrome:
http://localhost:8080/trigger.html
Expected output — vulnerable Chrome (< 157.0.8103.50):
[*] Chrome version: 157.0.8103.47 (VULNERABLE)
[*] serving PoC on http://0.0.0.0:8080
[*] request: GET /trigger.html (192.168.1.50)
[*] UAF triggered — renderer crash or controlled execution
[!] VULNERABLE — check Chrome crash report or renderer log
Expected output — patched Chrome (≥ 157.0.8103.50):
[*] Chrome version: 157.0.8103.50 (PATCHED)
[+] XML node lifecycle fix present — UAF trigger returns safe value
[+] NOT vulnerable
| Flag | Description |
|---|---|
--mode serve|craft | Serve HTTP or write trigger file only |
--port N | HTTP server port (default: 8080) |
--out FILE | Output HTML path for craft mode |
--host IP | Bind address (default: 0.0.0.0) |
The crafted page manipulates the XML parser into freeing a node while holding a live reference:
<!-- Simplified trigger pattern -->
<svg xmlns="http://www.w3.org/2000/svg">
<script>
// 1. Create XML document with linked nodes
// 2. Trigger node removal that frees backing memory
// 3. Access dangling reference before GC sweep
// 4. Spray controlled data into freed region
</script>
</svg>
| Indicator | Notes |
|---|---|
| Chrome renderer crash with signal 11 / SIGSEGV | Chrome crash report: --type=renderer |
| Chrome version < 157.0.8103.50 on endpoint | Asset inventory / vulnerability scanner |
| Unusual XML/SVG parsing activity in renderer | Browser telemetry / EDR renderer events |
| CISA KEV rule for CVE-2026-125350 | Scanner plugin (Tenable, Qualys, Rapid7) |
Sandbox-contained renderer code execution. An attacker who controls a web page the victim visits can execute arbitrary code in Chrome's renderer process. Full OS compromise requires chaining with a separate sandbox escape vulnerability.
Update Chrome to 157.0.8103.50 or later. Chrome auto-updates; force it via chrome://settings/help or fleet management.
| Action | Detail |
|---|---|
| Update Chrome | 157.0.8103.50 / .51 or any later stable build |
| Enable enhanced safe browsing | Blocks malicious URLs before page loads |
| Restrict untrusted page access | Zero-trust browser isolation or allow-list |
| CISA KEV deadline | 2026-11-24 for federal agencies |
Disclaimer: For authorized security research and controlled lab use only. MIT License.