CVE-2026-125350: Google Chromium Blink XML Engine Use-After-Free Remote Code Execution
A critical use-after-free (UAF) zero-day flaw in Google Chromium's Blink XML and XPath parsing engine (CVE-2026-125350, CVSS 8.8) was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on November 10, 2026. Exploited in targeted watering-hole attacks against enterprise personnel, the vulnerability is triggered when a victim browses to a maliciously crafted webpage. Premature reclamation of DOM nodes during asynchronous XML parsing corrupts browser memory, enabling attackers to execute arbitrary shellcode inside the sandboxed renderer process and escape to host execution when chained with kernel elevation exploits. Organizations must immediately deploy Google Chrome version 157.0.8103.50/.51 and equivalent updates for Microsoft Edge, Brave, and Electron-based enterprise desktop applications.
HERMES THREAT SCORE & ENDPOINT BROWSER RISK
Target:Google Chromium Blink XML Parser and Oilpan Garbage Collection Runtime While CVSS v3.1 rates this flaw at 8.8 (High) due to required user interaction (visiting a link), Hermes assigns an HTS score of 96 (CRITICAL). Active zero-day weaponization by advanced threat actors targeting corporate workstations, coupled with the engine's omnipresence across browsers and Electron frameworks, makes this vulnerability an acute initial access threat.
1. Executive Summary & Operational Context
Section titled โ1. Executive Summary & Operational ContextโThe Chromium browser engine powers the overwhelming majority of modern enterprise web browsing, including Google Chrome, Microsoft Edge, Opera, and thousands of enterprise collaboration suites built upon the Electron framework (e.g. Slack, Teams, VS Code).
On November 10, 2026, CISA cataloged CVE-2026-125350 following telemetry confirming active zero-day exploitation against corporate endpoints. By luring corporate users to infected websites or delivering malicious advertisements (malvertising), adversaries exploit memory corruption in Chromiumโs XML engine to bypass browser security boundaries.
2. Technical Vulnerability Analysis & Root Cause
Section titled โ2. Technical Vulnerability Analysis & Root CauseโThe flaw exists within Blinkโs XML/XPath processing subsystem (third_party/blink/renderer/core/xml/xpath_expression.cc).
When Chromium processes complex asynchronous XML documents containing dynamic DOM mutations and XPath expressions (document.evaluate()), the garbage collector (Oilpan) can prematurely free DOM node objects while an active expression iterator retains an un-traced raw pointer:
// Vulnerable sequence in XPathExpression::evaluateNode* current_node = context_node.Get(); // Raw pointer obtained without strong GC handle// Triggering asynchronous DOM mutation callback:xml_doc->DispatchSubtreeModifiedEvent();// Garbage collector runs: current_node is freed in Oilpan heapcurrent_node->lookupNamespaceURI(...); // Use-After-Free: accesses reclaimed memoryAn attacker uses JavaScript heap-spraying techniques to occupy the vacated memory slot with crafted object structures, redirecting virtual method table (vtable) dispatch pointers to execute arbitrary shellcode within the browser renderer process.
3. Attack Execution Flow & Weaponization Mechanics
Section titled โ3. Attack Execution Flow & Weaponization Mechanicsโflowchart TD A["Target Enterprise User"] -->|"Step 1: Navigates to Compromised Webpage<br/>(Drive-by Watering Hole)"| B["Google Chrome / Edge Browser"] B -->|"Step 2: Executes Obfuscated JavaScript"| C["Blink XML DOM Parser"] C -->|"Step 3: Triggers Asynchronous XPath Mutation"| D["Oilpan Garbage Collection"] D -->|"Frees Active DOM Node Object"| E["Use-After-Free State Created"] C -->|"Derefences Dangling Pointer"| F["Renderer Shellcode Execution"] F -->|"Step 4: Chains with OS Kernel Exploit"| G["Sandbox Escape & Full Host Takeover"]4. Forensic Signatures, Detection Queries & IOCs
Section titled โ4. Forensic Signatures, Detection Queries & IOCsโSigma Detection Rule
Section titled โSigma Detection Ruleโtitle: Browser Renderer Unusual Child Process Spawningid: 4e91b238-1253-4f99-b108-f81d12535001status: experimentaldescription: Detects unusual command interpreters spawned by browser renderer processes following CVE-2026-125350 exploitationlogsource: category: process_creationdetection: selection: ParentImage|endswith: - '\chrome.exe' - '\msedge.exe' - '\brave.exe' Image|endswith: - '\cmd.exe' - '\powershell.exe' - '\wscript.exe' - '\cscript.exe' condition: selectionlevel: criticalThreat Intelligence & Indicators of Compromise (IOCs)
Section titled โThreat Intelligence & Indicators of Compromise (IOCs)โ| Type | Indicator | Context |
|---|---|---|
| IP Address | 103.152.220[.]88 | Watering-hole exploit staging domain |
| IP Address | 194.38.20[.]114 | Malvertising redirect proxy |
| IP Address | 45.154.255[.]19 | Second-stage payload delivery server |
| Crash Signature | Status 0xC0000005 in chrome.dll | Access violation crash in Blink XPath module |
5. Comprehensive Remediation, Hardening & Mitigation Plan
Section titled โ5. Comprehensive Remediation, Hardening & Mitigation Planโ-
Deploy Emergency Browser Updates: Immediately roll out Google Chrome 157.0.8103.50/.51 (or later) and corresponding Microsoft Edge releases across all enterprise endpoints.
-
Update Electron Applications: Ensure corporate desktop applications leveraging embedded Chromium (Slack, Microsoft Teams, Zoom) are updated to packages incorporating patched Chromium builds.
-
Enable Enhanced Protection / Sandboxing: Enforce Google Chrome โEnhanced Protectionโ via enterprise administrative templates (GPO) to detect and block malicious script payloads proactively.
-
Monitor Renderer Crashes and EDR Telemetry: Configure SIEM alerting on elevated rates of browser renderer crashes (Event ID 1000 in Application logs) coupled with suspicious outbound network connections from endpoint workstations.