Threat Overview
Google’s November 9, 2026 Chrome Stable update addresses CVE-2026-125350, a high-severity use-after-free vulnerability in the XML component. Google explicitly states that an exploit exists in the wild. Public information does not identify an exploit chain, threat actor, delivery vector, or attacker infrastructure.
References
Google Chrome Releases, November 9, 2026: Stable Channel Update for Desktop.
Impacted Systems
Google Chrome desktop, Windows, macOS, and Linux, prior to the applicable fixed Stable release. Fixed: 157.0.8103.50/.51 for Windows and macOS; 157.0.8103.50 for Linux. The Extended Stable channel also received 156.0.8078.96 for Windows and macOS. No special configuration or exposed network listener is established as a prerequisite.
Why this matters
Chrome is widespread across managed endpoints, and the vendor confirms exploitation. Endpoint behavioral telemetry can identify suspicious execution and persistence following possible browser compromise, but cannot prove exploitation of this specific CVE without additional evidence.
Exploitation Status
Confirmed in-the-wild exploitation according to Google on November 9, 2026. No public IOC list or exploit-chain details were provided in the vendor release.
What this hunt looks for
Browser-initiated shell and script execution; browser-associated executable writes; rare external destinations; process-to-network correlation; suspicious persistence; and Defender alerts. These are post-compromise behavioral leads, not signatures for CVE-2026-125350.
Required logs
Microsoft Defender for Endpoint DeviceProcessEvents, DeviceNetworkEvents, DeviceFileEvents, DeviceRegistryEvents, and Microsoft Sentinel SecurityAlert where these sources are ingested. Run only the queries supported by each workspace’s confirmed tables and retention.
C01 — First pass: Chrome spawning command interpreters
DeviceProcessEvents
| where TimeGenerated >= ago(30d)
| where InitiatingProcessFileName in~ ("chrome.exe","chrome")
| where FileName in~ ("cmd.exe","powershell.exe","pwsh.exe","wscript.exe","cscript.exe","bash","sh","python.exe","python3")
| project TimeGenerated, DeviceName, AccountName, FileName, ProcessCommandLine, InitiatingProcessFileName, InitiatingProcessCommandLine
| order by TimeGenerated desc
C02 — Chrome-associated new external destinations
let Baseline = DeviceNetworkEvents
| where TimeGenerated between (ago(30d) .. ago(2d))
| where InitiatingProcessFileName in~ ("chrome.exe","chrome")
| summarize by DeviceId, RemoteIP;
DeviceNetworkEvents
| where TimeGenerated >= ago(2d)
| where InitiatingProcessFileName in~ ("chrome.exe","chrome")
| where isnotempty(RemoteIP) and not(ipv4_is_private(RemoteIP))
| join kind=leftanti Baseline on DeviceId, RemoteIP
| project TimeGenerated, DeviceName, RemoteIP, RemotePort, InitiatingProcessFileName, InitiatingProcessCommandLine
| order by TimeGenerated desc
C03 — Executable or script files written by Chrome
DeviceFileEvents
| where TimeGenerated >= ago(30d)
| where InitiatingProcessFileName in~ ("chrome.exe","chrome")
| where FileName endswith ".exe" or FileName endswith ".dll" or FileName endswith ".ps1" or FileName endswith ".vbs" or FileName endswith ".sh"
| project TimeGenerated, DeviceName, ActionType, FileName, FolderPath, InitiatingProcessFileName, InitiatingProcessCommandLine
| order by TimeGenerated desc
C04 — Suspicious execution followed by external network activity
let Child = DeviceProcessEvents
| where TimeGenerated >= ago(30d)
| where InitiatingProcessFileName in~ ("chrome.exe","chrome")
| where FileName in~ ("powershell.exe","pwsh.exe","cmd.exe","bash","sh","python.exe","python3")
| project DeviceId, ProcessId, ProcessTime=TimeGenerated, DeviceName, FileName, ProcessCommandLine;
let Net = DeviceNetworkEvents
| where TimeGenerated >= ago(30d)
| where isnotempty(RemoteIP) and not(ipv4_is_private(RemoteIP))
| project DeviceId, InitiatingProcessId, NetTime=TimeGenerated, RemoteIP, RemotePort;
Child
| join kind=inner Net on DeviceId
| where ProcessId == InitiatingProcessId and NetTime between (ProcessTime .. ProcessTime + 10m)
| project ProcessTime, NetTime, DeviceName, FileName, ProcessCommandLine, RemoteIP, RemotePort
| order by NetTime desc
C05 — Chrome-associated registry persistence changes
DeviceRegistryEvents
| where TimeGenerated >= ago(30d)
| where InitiatingProcessFileName in~ ("chrome.exe","chrome")
| where RegistryKey has_any ("\\CurrentVersion\\Run","\\CurrentVersion\\RunOnce","\\CurrentVersion\\Policies\\Explorer\\Run")
| project TimeGenerated, DeviceName, ActionType, RegistryKey, RegistryValueName, RegistryValueData, InitiatingProcessFileName
| order by TimeGenerated desc
C06 — Defender alerts mentioning Chrome and exploit activity
SecurityAlert
| where TimeGenerated >= ago(30d)
| where (AlertName has_any ("browser","exploit","chrome") or Description has_any ("chrome.exe","browser exploit"))
| project TimeGenerated, AlertName, AlertSeverity, ProviderName, CompromisedEntity, Description
| order by TimeGenerated desc
C07 — Chrome spawning download or LOLBin utilities
DeviceProcessEvents
| where TimeGenerated >= ago(30d)
| where InitiatingProcessFileName in~ ("chrome.exe","chrome")
| where FileName in~ ("certutil.exe","bitsadmin.exe","mshta.exe","rundll32.exe","regsvr32.exe","curl.exe","wget","curl")
| project TimeGenerated, DeviceName, AccountName, FileName, ProcessCommandLine, InitiatingProcessCommandLine
| order by TimeGenerated desc
Detection Notes
Highest-signal leads are unexpected browser-to-shell execution followed by external connections. Chrome normally writes downloaded files and connects to new destinations, so those hunts are noisy without process, user, and destination context. Browser sandboxing can obscure direct parent-child relationships. Registry persistence covers Windows only. Missing Defender endpoint tables or limited retention can make these behaviors invisible in Sentinel. No customer-specific Sentinel workspaces were queried; no findings or absence of compromise are asserted.