Threat reportVulnerabilityTL-2026-6328
Chrome 158 Fixes 204 Vulnerabilities Including Six Critical Code Execution Flaws (CVE-2026-130963, CVE-2026-131031, CVE-2026-131060, CVE-2026-131008, CVE-2026-131054, CVE-2026-130975)
Google's Chrome 158 stable release (rollout began 2026-11-17) patches 204 security issues, six rated Critical (use-after-free, out-of-bounds write and buffer overflow in WebView, GPU, Media, GarbageCollection, ANGLE and WebAudio). No in-the-wild exploitation is flagged for these CVEs; NVD SSVC data lists exploitation as 'none'.
Key facts
| Identifiers | TL-2026-6328, CVE-2026-130963, CVE-2026-131031, CVE-2026-131060, CVE-2026-131008, CVE-2026-131054, CVE-2026-130975, CVE-2026-130910, CVE-2026-131030, CVE-2026-131087, CVE-2026-131013 |
|---|---|
| Severity | CRITICAL |
| CVSS | 9.6 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H) |
| First disclosed | |
| Affected products | Google Chrome (Windows, macOS, Linux); Google Chrome for Android (CVE-2026-130963 WebView, CVE-2026-130910 ANGLE) |
| Weaknesses (CWE) | CWE-416, CWE-787, CWE-122, CWE-693, CWE-120 |
| MITRE ATT&CK techniques | T1068 Exploitation for Privilege Escalation, T1189 Drive-by Compromise, T1203 Exploitation for Client Execution, T1204.001 User Execution: Malicious Link, T1211 Exploitation for Stealth |
| Motivation | UNKNOWN |
| Target sectors | all sectors, enterprise, government administration, consumer |
| Target regions | Global |
| Detection rules | 9 (1 shown free) |
| Sources | 12 cited sources |
Detection coverage
As of 2026-11-18, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-6328 across Splunk SPL, Microsoft KQL and Sigma, covering 8 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.
Free detection: Chrome Browser Spawning Command Shell or Script Host - Post-Exploitation After Memory Corruption
Detects chrome.exe as parent of cmd.exe, powershell.exe, pwsh.exe, wscript.exe or cscript.exe. Chrome does not normally launch interpreters, so this is a high-fidelity sign of code execution after a browser exploit (T1203) such as the sandbox-escape flaws CVE-2026-131031 (GPU) and CVE-2026-131054 (ANGLE), followed by command execution (T1059.001, T1059.003).
- Languages: Splunk SPL, Microsoft KQL, Sigma
- ATT&CK: T1203, T1059.001, T1059.003
- Data sources: sysmon (index=sysmon, XmlWinEventLog:Microsoft-Windows-Sysmon/Operational, EventCode 1), Microsoft Defender for Endpoint DeviceProcessEvents
- Severity: high
- Confidence: high
Splunk SPL
index=sysmon sourcetype="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational" EventCode=1 ParentImage="*\\chrome.exe" earliest=-24h
(Image="*\\cmd.exe" OR Image="*\\powershell.exe" OR Image="*\\pwsh.exe" OR Image="*\\wscript.exe" OR Image="*\\cscript.exe")
| stats count AS executions, min(_time) AS first_seen, max(_time) AS last_seen, values(CommandLine) AS commands, values(ParentCommandLine) AS parent_cmd BY host, User, Image
| convert ctime(first_seen) ctime(last_seen)
| eval note="Interpreter spawned by Chrome - possible exploitation (CVE-2026-131031 CVE-2026-131054 CVE-2026-131060)"Microsoft KQL
DeviceProcessEvents
| where Timestamp > ago(24h)
| where InitiatingProcessFileName =~ "chrome.exe"
| where FileName in~ ("cmd.exe", "powershell.exe", "pwsh.exe", "wscript.exe", "cscript.exe")
| project Timestamp, DeviceName, AccountName, FileName, ProcessCommandLine, InitiatingProcessCommandLine, InitiatingProcessVersionInfoProductVersion, SHA256
| order by Timestamp descSigma
title: "Google Chrome Spawning Command Shell or Script Host"
id: b7a3c5d8-9e12-4f60-8b4a-2d1c6e7f0a05
status: experimental
description: "Detects chrome.exe launching cmd.exe, PowerShell, wscript or cscript. Indicates possible code execution following a Chrome memory-corruption exploit (CVE-2026-131031, CVE-2026-131054, CVE-2026-131060)."
references:
- https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop_01699533288.html
- https://nvd.nist.gov/vuln/detail/CVE-2026-131031
- https://cybersecuritynews.com/chrome-158-fixes-204-vulnerabilities/
author: Threadlinqs Team
date: 2026-11-18
tags:
- attack.execution
- attack.t1203
- attack.t1059.001
- attack.t1059.003
- cve.2026.131031
- cve.2026.131054
logsource:
category: process_creation
product: windows
detection:
selection:
ParentImage|endswith: '\chrome.exe'
Image|endswith:
- '\cmd.exe'
- '\powershell.exe'
- '\pwsh.exe'
- '\wscript.exe'
- '\cscript.exe'
condition: selection
falsepositives:
- Chrome native-messaging hosts or extensions that wrap a batch file
- Admin tooling launched from web-based consoles via custom URL handlers
level: high
Known false positives:
- Native-messaging hosts or enterprise extensions that launch cmd.exe wrappers
- Custom protocol handlers (for example remote support tools) invoked from the browser
Tuning notes: Allowlist known native-messaging host command lines by CommandLine hash or path. Treat any PowerShell with encoded commands or download strings as critical and isolate the host. Combine with vulnerable-build exposure for prioritisation.
- Chrome GPU Process Restart Burst - Possible GPU/ANGLE Memory-Corruption Crash Loop · unlock with TL Creds
- Chrome-Spawned Non-Browser Process Running Elevated - Sandbox Escape / Privilege Escalation Indicator · unlock with TL Creds
- Chrome-Spawned Download Cradle (certutil, bitsadmin, curl, PowerShell Web Download) · unlock with TL Creds
- Chrome Launched With Sandbox or Site-Isolation Disabled (Exploit Mitigation Weakening) · unlock with TL Creds
- Chrome Renderer, GPU or Utility Process Spawning a Non-Browser Child - Sandboxed Code Execution · unlock with TL Creds
- Chrome Spawning Signed-Binary Proxy Execution With Remote Content (mshta, rundll32, regsvr32) · unlock with TL Creds
- Vulnerable Chrome Build (< 158.0.8127.36) Executing - Chrome 158 Critical Memory-Corruption CVEs · unlock with TL Creds
- Process Spawned by Chrome Making Outbound Network Connections - Post-Exploit C2 Callback · unlock with TL Creds
Indicators of compromise
As of 2026-11-18, Threadlinqs Intelligence tracks 8 indicators of compromise for TL-2026-6328.
Technical analysis
Google released Chrome 158 to the stable channel on 2026-11-17 (Windows, macOS, Linux), with fixed builds 158.0.8127.36 (Linux) and 158.0.8127.36/.37 (Windows, macOS). The release carries 204 security fixes. Six are rated Critical by Chromium: CVE-2026-130963 (use-after-free in WebView), CVE-2026-131031 (out-of-bounds write in GPU), CVE-2026-131060 (buffer overflow in Media), CVE-2026-131008 (use-after-free in GarbageCollection), CVE-2026-131054 (out-of-bounds write in ANGLE) and CVE-2026-130975 (use-after-free in WebAudio). The press coverage credits Xinyang Ge (Anthropic) for CVE-2026-131031, CVE-2026-131060, CVE-2026-131008 and CVE-2026-130975, with Claude assisting on the first two; CVE-2026-130963 and CVE-2026-131054 are credited to Google.
Per the NVD records (status Awaiting/Undergoing Analysis at time of research), the trigger for the Chrome desktop flaws is a crafted HTML page that requires user interaction (visiting or opening it). CVE-2026-131031 (GPU) and CVE-2026-131054 (ANGLE) are described as allowing arbitrary code execution outside the sandbox (secondary-source CVSS 3.1 9.6, scope changed). CVE-2026-131060 (Media), CVE-2026-131008 (GarbageCollection) and CVE-2026-130975 (WebAudio) are described as code execution inside the sandbox (CVSS 3.1 8.8). The NVD record for CVE-2026-130963 describes the WebView use-after-free as affecting Chrome on Android, reachable by crafted network traffic, with code execution outside the browser sandbox; it carries no CVSS score. CVE-2026-130910 is a High-severity protection-mechanism failure in ANGLE on Android (CWE-693, secondary CVSS 9.6). The release also fixes High-severity bugs in V8, Autofill, extensions and downloads without published CVE IDs.
No public PoC, attribution, threat actor or network IOCs are stated in any source. NVD SSVC v2.0.3 data for the CVEs lists exploitation 'none', automatable 'no', technical impact 'total'. None of the CVEs were seen in the portion of the CISA KEV catalog that could be read; this was only a partial read. The press article refers to a separate earlier November Chrome zero-day exploited in attacks, which is not part of this record; CISA KEV separately lists CVE-2026-125350 (Chromium use-after-free) added 2026-11-10. Defenders should update Chrome and other Chromium-based browsers to the fixed build and verify fleet versions; since the vulnerabilities are patched and unexploited as far as is known, the priority is rapid patch deployment and monitoring for renderer or GPU process crashes.
MITRE ATT&CK techniques by tactic:
Privilege Escalation
T1068 Exploitation for Privilege Escalation
Initial Access
Execution
T1203 Exploitation for Client Execution; T1204.001 User Execution: Malicious Link
Stealth
Remediation
Patches
- Chrome 158.0.8127.36 (Linux)
- Chrome 158.0.8127.36/158.0.8127.37 (Windows, macOS)
Immediate actions
- Update Google Chrome to 158.0.8127.36 or later (158.0.8127.36/.37 on Windows and macOS) and relaunch the browser
- Update Chrome on Android to 158.0.8127.36 or later (CVE-2026-130963, CVE-2026-130910 are listed for Android)
- Verify browser version compliance across the fleet via endpoint management or EDR inventory
Workarounds
- No vendor workaround stated; limit browsing of untrusted sites on unpatched browsers until updated
Longer-term hardening
- Keep Chrome auto-update enabled and enforce relaunch deadlines through enterprise policy
- Update other Chromium-based browsers (Edge, Opera, Brave) when their vendors ship the Chrome 158 fixes
- Monitor Chrome renderer, GPU and utility process crashes as a hunting signal
Affected and fixed versions
- Google — Chrome (Windows, macOS, Linux)
Vulnerable versions: prior to 158.0.8127.36
Fixed in: 158.0.8127.36 (Linux); 158.0.8127.36/158.0.8127.37 (Windows, macOS) - Google — Chrome for Android (CVE-2026-130963 WebView, CVE-2026-130910 ANGLE)
Vulnerable versions: prior to 158.0.8127.36
Fixed in: 158.0.8127.36
Timeline
Last updated · revalidated 1× · latest source
- Chrome 157 (157.0.8103.38/39) released with over 200 security fixes, some critical; PCWorld noted Chrome 158 was due in two weeks
- CISA added the separate Chromium use-after-free CVE-2026-125350 to KEV (not part of this record; due date 2026-11-24)
- Google states bug details may stay restricted until a majority of users are updated, or longer if a third-party library is still unpatched.
- Advisory also itemizes roughly 60 High-severity fixes, including CVE-2026-130910 (ANGLE, $4,000 bounty to Arni Hardarson of Neonix Security) and CVE-2026-131013 (Skia buffer overflow), plus Medium issues CVE-2026-131030 (sandbox privilege elevation) and CVE-2026-131087 (V8 type confusion).
- NVD published records for CVE-2026-130963, CVE-2026-131031, CVE-2026-131060, CVE-2026-131008, CVE-2026-131054, CVE-2026-130975 and CVE-2026-130910, status Awaiting Analysis
- Google began rolling out Chrome 158 stable (158.0.8127.36/.37) on Windows, macOS and Linux with 204 security fixes, six Critical
- Cyber Security News reported the release; Google did not flag active exploitation or state whether any flaw escapes the sandbox
- NVD records updated with secondary CVSS 3.1 scores (8.8 to 9.6) and CISA SSVC data showing exploitation 'none'
Update history
- 2026-11-18 — Google Chrome 158 Stable Update: 204 Security Fixes Including 6 Critical Vulnerabilities (CVE-2026-130963, CVE-2026-131031, CVE-2026-131060, CVE-2026-131008, CVE-2026-131054, CVE-2026-130975): What changed No change to severity (CRITICAL), exploitability (THEORETICAL retained; the new report's NONE is not an escalation) or status (PATCHED). Record is extended with additional CVEs from the same advisory.
Sources cited
- NVD CVE-2026-131031 NVD (NIST) · Advisory · 2026-11-17
- NVD CVE-2026-131054 NVD (NIST) · Advisory · 2026-11-17
- NVD CVE-2026-131060 NVD (NIST) · Advisory · 2026-11-17
- NVD CVE-2026-131008 NVD (NIST) · Advisory · 2026-11-17
- NVD CVE-2026-130975 NVD (NIST) · Advisory · 2026-11-17
- NVD CVE-2026-130963 NVD (NIST) · Advisory · 2026-11-17
- NVD CVE-2026-130910 NVD (NIST) · Advisory · 2026-11-17
- CISA Known Exploited Vulnerabilities Catalog CISA · Government advisory · 2026-11-10
- Chromium issue 571153713 (CVE-2026-131031) issues.chromium.org · Advisory · 2026-11-17
- Stable Channel Update for Desktop (Chrome Releases) chromereleases.googleblog.com · Vendor report · 2026-11-17
- Chrome 158 Fixes 204 Vulnerabilities, Including Critical Code Execution Flaws cybersecuritynews.com · News · 2026-11-18
- Chrome 157 fixes over 200 security flaws, 7 critical (PCWorld) pcworld.com · News · 2026-11-04
Drafted by the Threadlinqs research pipeline from 12 sources; published ; last updated .