# 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'.

- **Published:** 2026-11-18T10:52:54Z
- **Last reviewed:** 2026-11-18T12:17:54.351Z
- **Canonical:** https://intel.threadlinqs.com/threat/TL-2026-6328
- **ID:** TL-2026-6328
- **Severity:** CRITICAL (CVSS 9.6)
- **Category:** VULNERABILITY
- **Status:** PATCHED
- **Detections:** 9 (1 shown free below) · **IOCs:** 8
- **CVEs:** 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

## Description

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

- T1203 Exploitation for Client Execution
- T1204.001 User Execution: Malicious Link
- T1211 Exploitation for Stealth
- T1189 Drive-by Compromise
- T1068 Exploitation for Privilege Escalation

## Free detection (Splunk SPL, Microsoft KQL, Sigma)

**Chrome Browser Spawning Command Shell or Script Host - Post-Exploitation After Memory Corruption** (`TL-2026-6328-SPL-002`)

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

```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

```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 desc
```

### Sigma

```yaml
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.

### 8 more detection rules (Splunk SPL, Microsoft KQL, Sigma), unlock with TL Creds

- Chrome GPU Process Restart Burst - Possible GPU/ANGLE Memory-Corruption Crash Loop (locked: unlock with TL Creds)
- Chrome-Spawned Non-Browser Process Running Elevated - Sandbox Escape / Privilege Escalation Indicator (locked: unlock with TL Creds)
- Chrome-Spawned Download Cradle (certutil, bitsadmin, curl, PowerShell Web Download) (locked: unlock with TL Creds)
- Chrome Launched With Sandbox or Site-Isolation Disabled (Exploit Mitigation Weakening) (locked: unlock with TL Creds)
- Chrome Renderer, GPU or Utility Process Spawning a Non-Browser Child - Sandboxed Code Execution (locked: unlock with TL Creds)
- Chrome Spawning Signed-Binary Proxy Execution With Remote Content (mshta, rundll32, regsvr32) (locked: unlock with TL Creds)
- Vulnerable Chrome Build (< 158.0.8127.36) Executing - Chrome 158 Critical Memory-Corruption CVEs (locked: unlock with TL Creds)
- Process Spawned by Chrome Making Outbound Network Connections - Post-Exploit C2 Callback (locked: unlock with TL Creds)

Sign up free to unlock the detection rules: https://threadlinqs.com/?modal=signup

## Sources

- [Chrome 158 Fixes 204 Vulnerabilities, Including Critical Code Execution Flaws](https://cybersecuritynews.com/chrome-158-fixes-204-vulnerabilities/)
- [Stable Channel Update for Desktop (Chrome Releases)](https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop_01699533288.html)
- [NVD CVE-2026-131031](https://nvd.nist.gov/vuln/detail/CVE-2026-131031)
- [NVD CVE-2026-131054](https://nvd.nist.gov/vuln/detail/CVE-2026-131054)
- [NVD CVE-2026-131060](https://nvd.nist.gov/vuln/detail/CVE-2026-131060)
- [NVD CVE-2026-131008](https://nvd.nist.gov/vuln/detail/CVE-2026-131008)
- [NVD CVE-2026-130975](https://nvd.nist.gov/vuln/detail/CVE-2026-130975)
- [NVD CVE-2026-130963](https://nvd.nist.gov/vuln/detail/CVE-2026-130963)
- [NVD CVE-2026-130910](https://nvd.nist.gov/vuln/detail/CVE-2026-130910)
- [CISA Known Exploited Vulnerabilities Catalog](https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json)
- [Chromium issue 571153713 (CVE-2026-131031)](https://issues.chromium.org/issues/571153713)
- [Chrome 157 fixes over 200 security flaws, 7 critical (PCWorld)](https://pcworld.com/article/3276837/chrome-157-fixes-over-200-security-flaws-7-of-them-critical.html)

## Full data

The other 8 detection rules (Splunk SPL / Microsoft KQL / Sigma) unlock with TL Creds; a free account includes daily creds: https://threadlinqs.com/?modal=signup
Indicator values unlock with TL Creds, at a lower price on Red and Purple; AI agents can query rules and IOCs through the Threadlinqs MCP server (Purple): https://intel.threadlinqs.com/mcp

Canonical: https://intel.threadlinqs.com/threat/TL-2026-6328
