Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
Tools/GitHubGitHub/llcforge/cve-2026-125350
Vulnerability AnalysisExploitationWeb Application ExploitationRed Teaming
GitHubllcforge/cve-2026-125350

CVE-2026-125350

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).

View Repository
15h 11m agoNot yet reviewed
Share

CVE-2026-125350

Google Chrome — XML Parser Use-After-Free (8th Zero-Day of 2026)

CVSS CWE Language KEV Fixed Disclosed


Overview

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.

FieldValue
CVECVE-2026-125350
CVSS 3.18.8 High — AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
CWECWE-416 (Use After Free)
ComponentChrome XML parser (Blink/libxml2 integration)
AffectedGoogle Chrome < 157.0.8103.50
FixedChrome 157.0.8103.50 / 157.0.8103.51 (2026-11-09)
KEVCISA added 2026-11-10, federal deadline 2026-11-24
Auth RequiredNone — victim visits a crafted page
Disclosed2026-11-09

Vulnerability Details

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.


Attack Flow

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

PoC Usage

Warning: Lab environment only. The trigger HTML requires Chrome < 157.0.8103.50. Use an isolated VM — do not run on production systems.

Setup

# 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

Check Chrome version

# 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

Trigger the UAF

# 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

Available flags

FlagDescription
--mode serve|craftServe HTTP or write trigger file only
--port NHTTP server port (default: 8080)
--out FILEOutput HTML path for craft mode
--host IPBind address (default: 0.0.0.0)

Trigger HTML structure

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>

Detection

IndicatorNotes
Chrome renderer crash with signal 11 / SIGSEGVChrome crash report: --type=renderer
Chrome version < 157.0.8103.50 on endpointAsset inventory / vulnerability scanner
Unusual XML/SVG parsing activity in rendererBrowser telemetry / EDR renderer events
CISA KEV rule for CVE-2026-125350Scanner plugin (Tenable, Qualys, Rapid7)

Impact

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.


Remediation

Update Chrome to 157.0.8103.50 or later. Chrome auto-updates; force it via chrome://settings/help or fleet management.

ActionDetail
Update Chrome157.0.8103.50 / .51 or any later stable build
Enable enhanced safe browsingBlocks malicious URLs before page loads
Restrict untrusted page accessZero-trust browser isolation or allow-list
CISA KEV deadline2026-11-24 for federal agencies

References

  • Google Chrome Releases: https://chromereleases.googleblog.com/
  • BleepingComputer: https://bleepingcomputer.com/news/security/google-patches-eighth-chrome-zero-day-exploited-in-attacks-this-year
  • SOCRadar: https://socradar.io/blog/cve-2026-125350-google-chrome-xml-0day/
  • CISA KEV: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
  • CVE Record: https://www.cve.org/CVERecord?id=CVE-2026-125350

Disclaimer: For authorized security research and controlled lab use only. MIT License.

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    851
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    538
  • 3

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    420
  • 4

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    357
  • 5

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    297
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    280

Explore all tools

Browse our collection of tools

View all tools →