Threat reportVulnerabilityTL-2026-3801
Google Chrome 155 Security Update Fixes 10 Vulnerabilities Including Critical Prerender Use-After-Free (CVE-2026-110922)
Google released Chrome 155.0.8059.84/.85 (Windows/Mac) and 155.0.8059.84 (Linux) on 2026-10-15, fixing 10 vulnerabilities: 1 Critical (Prerender use-after-free), 6 High (DOM, three in V8, Core, SVG) and 3 Medium. Google has not stated that any issue is exploited in the wild.
Key facts
| Identifiers | TL-2026-3801, CVE-2026-110922, CVE-2026-110913, CVE-2026-110919, CVE-2026-110918, CVE-2026-110917, CVE-2026-110921, CVE-2026-110920, CVE-2026-110916, CVE-2026-110915, CVE-2026-110914 |
|---|---|
| Severity | CRITICAL |
| CVSS | 8.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) |
| EPSS | CVE-2026-110922: 0.3% (32.4th percentile); CVE-2026-110916: 0.3% (30.1th percentile); CVE-2026-110913: 0.3% (25.5th percentile) |
| Affected products | Google Chrome (Windows, macOS, Linux) |
| Weaknesses (CWE) | CWE-416, CWE-119 |
| MITRE ATT&CK techniques | T1059.007 Command and Scripting Interpreter, T1068 Exploitation for Privilege Escalation, T1189 Drive-by Compromise, T1203 Exploitation for Client Execution, T1204 User Execution, T1204.001 User Execution, T1211 Exploitation for Defense Evasion, T1566 Phishing |
| Motivation | UNKNOWN |
| Target sectors | technology, government administration, finance, health, education, enterprise |
| Target regions | Global |
| Detection rules | 9 (1 shown free) |
| Sources | 6 cited sources |
Detection coverage
As of 2026-10-17, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-3801 across Splunk SPL, Microsoft KQL and Sigma, covering 9 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 Spawning Script Interpreter or LOLBin — CVE-2026-110922 Exploitation
Fires when chrome.exe launches cmd, PowerShell, mshta, rundll32, regsvr32 and similar binaries. Memory-corruption bugs fixed in Chrome 155.0.8059.84 (CVE-2026-110922, CVE-2026-110913, CVE-2026-110919, CVE-2026-110921, CVE-2026-110920, CVE-2026-110917) are renderer-stage flaws usually chained with a sandbox escape; a browser process spawning an interpreter is the most reliable endpoint signal. No in-the-wild exploitation is reported, so treat hits as high-priority anomalies.
- Languages: Splunk SPL, Microsoft KQL, Sigma
- ATT&CK: T1189, T1203, T1204.001, T1068
- Data sources: sysmon, microsoft_defender_for_endpoint, windows_process_creation
- Severity: high
- Confidence: high
Splunk SPL
```TL-2026-3801 exploitation: Chrome (CVE-2026-110922 Prerender UAF / V8 / DOM memory corruption) spawning interpreters or LOLBins```
index=sysmon sourcetype="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational" EventCode=1 earliest=-24h
ParentImage="*\\chrome.exe" (Image="*\\cmd.exe" OR Image="*\\powershell.exe" OR Image="*\\pwsh.exe" OR Image="*\\wscript.exe" OR Image="*\\cscript.exe" OR Image="*\\mshta.exe" OR Image="*\\rundll32.exe" OR Image="*\\regsvr32.exe" OR Image="*\\msbuild.exe" OR Image="*\\certutil.exe" OR Image="*\\bitsadmin.exe" OR Image="*\\wmic.exe" OR Image="*\\curl.exe" OR Image="*\\installutil.exe")
| eval parent_role=case(match(ParentCommandLine,"--type=renderer"),"renderer", match(ParentCommandLine,"--type="),"helper", true(),"browser")
| table _time host User parent_role ParentImage ParentCommandLine Image CommandLine ProcessGuid
| sort - _timeMicrosoft KQL
DeviceProcessEvents
| where Timestamp > ago(24h)
| where InitiatingProcessFileName =~ "chrome.exe"
| where FileName in~ ("cmd.exe","powershell.exe","pwsh.exe","wscript.exe","cscript.exe","mshta.exe","rundll32.exe","regsvr32.exe","msbuild.exe","certutil.exe","bitsadmin.exe","wmic.exe","curl.exe","installutil.exe")
| extend ChromeVersion = InitiatingProcessVersionInfoProductVersion
| extend ParentRole = case(InitiatingProcessCommandLine has "--type=renderer", "renderer", InitiatingProcessCommandLine has "--type=", "helper", "browser")
| extend VulnerableBuild = iff(isnotempty(ChromeVersion) and parse_version(ChromeVersion) < parse_version("155.0.8059.84"), true, false)
| project Timestamp, DeviceName, AccountName, ParentRole, ChromeVersion, VulnerableBuild, InitiatingProcessCommandLine, FileName, ProcessCommandLine, SHA256
| order by Timestamp descSigma
title: Chrome Spawning Script Interpreter or LOLBin (CVE-2026-110922 Exploitation)
id: 5b0c3a52-7d1e-4f0a-9c61-3801a0000001
status: experimental
description: Detects chrome.exe spawning command interpreters or living-off-the-land binaries, a post-exploit or sandbox-escape indicator for Chrome memory-corruption bugs such as CVE-2026-110922 (Prerender UAF) fixed in 155.0.8059.84.
references:
- https://chromereleases.googleblog.com/2026/10/
- https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-110922
- https://intel.threadlinqs.com
author: Threadlinqs Team
date: 2026/10/17
tags:
- attack.initial-access
- attack.t1189
- attack.execution
- attack.t1203
- attack.t1204.001
- attack.privilege-escalation
- attack.t1068
- cve.2026-110922
logsource:
category: process_creation
product: windows
detection:
selection_parent:
ParentImage|endswith: '\chrome.exe'
selection_child:
Image|endswith:
- '\cmd.exe'
- '\powershell.exe'
- '\pwsh.exe'
- '\wscript.exe'
- '\cscript.exe'
- '\mshta.exe'
- '\rundll32.exe'
- '\regsvr32.exe'
- '\msbuild.exe'
- '\certutil.exe'
- '\bitsadmin.exe'
- '\wmic.exe'
- '\curl.exe'
- '\installutil.exe'
condition: selection_parent and selection_child
falsepositives:
- Enterprise web apps or helper extensions that launch scripts via native messaging
- Developer or IT workflows launching cmd.exe from Chrome-based tools
level: high
Known false positives:
- Native messaging hosts or enterprise extensions that launch scripts via chrome.exe
- IT tooling that starts cmd.exe from Chrome
Tuning notes: Allowlist known native messaging host command lines. Raise priority when parent_role=renderer or VulnerableBuild=true. Join with software inventory to prioritise hosts below 155.0.8059.84.
- Chrome Spawning Script Interpreter or LOLBin — CVE-2026-110922 Exploitation (KQL primary) · unlock with TL Creds
- Chrome Dropping Executable or Script Outside Downloads — Post-Exploitation Staging (KQL primary) · unlock with TL Creds
- Chrome-Spawned Process With Download Cradle or Remote URL — C2 Staging (KQL primary) · unlock with TL Creds
- Chrome Spawning Script Interpreter or LOLBin — CVE-2026-110922 Exploitation (Sigma primary) · unlock with TL Creds
- Chrome Dropping Executable or Script Outside Downloads — Post-Exploitation Staging (Sigma primary) · unlock with TL Creds
- Chrome-Spawned Process With Download Cradle or Remote URL — C2 Staging (Sigma primary) · unlock with TL Creds
- Chrome Dropping Executable or Script Outside Downloads — Post-Exploitation Staging · unlock with TL Creds
- Chrome-Spawned Process With Download Cradle or Remote URL — C2 Staging · unlock with TL Creds
Indicators of compromise
As of 2026-10-17, Threadlinqs Intelligence tracks 9 indicators of compromise for TL-2026-3801.
Technical analysis
The Chrome stable-channel update to 155.0.8059.84/.85 (Windows/Mac) and 155.0.8059.84 (Linux) addresses 10 security issues. The single Critical-rated flaw, CVE-2026-110922, is a use-after-free in the Prerender component reported by Xinyang Ge of Anthropic on 2026-10-02. NVD describes it as allowing a remote attacker to execute arbitrary code inside the browser sandbox via a crafted HTML page; user interaction (visiting a malicious page) is required. NVD lists it as CWE-416 with a CVSS 3.1 base score of 8.8 and affected versions earlier than 155.0.8059.84, while Chromium rates it Critical. NVD references Chromium issue 568719351.
Six High-severity issues are fixed: CVE-2026-110913 (DOM, memory corruption, reported 2026-09-29 by Xinyang Ge with Claude AI assistance, which Google credited publicly), CVE-2026-110919 and CVE-2026-110921 (V8 use-after-free), CVE-2026-110920 (V8 memory corruption), CVE-2026-110918 (Core memory corruption, found by Google) and CVE-2026-110917 (SVG memory corruption, reported by C0rk1). Three Medium issues are CVE-2026-110916 (Desktop, improper input validation), CVE-2026-110915 (Compositing use-after-free) and CVE-2026-110914 (Workers memory corruption), all credited to Google.
The release follows the initial Chrome 155 stable release of 2026-10-07 (155.0.8059.39/.40), which patched 247 vulnerabilities including four Critical use-after-free flaws, many reported by Xinyang Ge with AI assistance. Per secondary reporting, the vendor made no mention of in-the-wild exploitation, bounty amounts for the Claude-assisted reports were not paid, and technical details are restricted until most users update. No PoC, exploit code, threat actor, malware or network IOCs are associated with these CVEs in the reviewed sources. Several details (Chromium release-note text for 155.0.8059.84, per-CVE NVD CVSS for the other nine CVEs) could not be verified directly from the primary Chrome Releases post.
Defender relevance: memory-corruption bugs in the renderer-facing components (V8, DOM, SVG, Prerender) are a common first stage of browser exploit chains, typically paired with a separate sandbox escape. Because Chrome auto-updates gradually over days to weeks, endpoints can stay exposed after release. Priority is fleet-wide version enforcement rather than IOC blocking.
MITRE ATT&CK techniques by tactic:
Execution
T1059.007 Command and Scripting Interpreter; T1203 Exploitation for Client Execution; T1204 User Execution; T1204.001 User Execution
Privilege Escalation
T1068 Exploitation for Privilege Escalation
Initial Access
T1189 Drive-by Compromise; T1566 Phishing
Defense Evasion
Remediation
Patches
- Chrome 155.0.8059.84/.85 (Windows/macOS) and 155.0.8059.84 (Linux)
Immediate actions
- Update Google Chrome to 155.0.8059.84 or later (155.0.8059.84/.85 on Windows and macOS) and relaunch the browser to apply the update
- Verify the deployed version via chrome://version or endpoint inventory and flag hosts below 155.0.8059.84
- Update other Chromium-based browsers (Edge, Brave, Opera, Vivaldi) as soon as their vendors ship the corresponding Chromium 155 fixes
Workarounds
- No vendor workaround documented; restrict browsing to untrusted sites from unpatched hosts until updated
- Use Enhanced Safe Browsing and block known-malicious web content at the proxy
Longer-term hardening
- Enforce managed browser auto-update and a maximum relaunch deferral through enterprise policy
- Keep Chrome Site Isolation and the renderer sandbox enabled
- Monitor Chrome Releases and CISA KEV for later reports of exploitation of these CVEs
Affected and fixed versions
- Google — Chrome (Windows, macOS, Linux)
Vulnerable versions: Versions prior to 155.0.8059.84
Fixed in: 155.0.8059.84/.85 (Windows/Mac); 155.0.8059.84 (Linux)
Timeline
Last updated · revalidated 1× · latest source
- CVE-2026-110916 (Desktop improper input validation, Medium) reported to Google; the oldest report in the batch.
- CVE-2026-110913 (DOM memory corruption) reported to Google by Xinyang Ge with Claude AI assistance
- CVE-2026-110922 (Prerender use-after-free, Critical) reported to Google by Xinyang Ge of Anthropic
- Initial Chrome 155 stable release (155.0.8059.39/.40) published with 247 security fixes, including four Critical use-after-free flaws; no in-the-wild exploitation stated
- Chrome 155.0.8059.79/.80 reportedly released fixing 37 other flaws (8 critical, 23 high, 5 medium, 1 low) per SecurityOnline, with Xinyang Ge credited for 16; 155.0.8059.84/.85 is the follow-up release.
- NVD record for CVE-2026-110922 describes it as a CWE-416 use-after-free in Prerender affecting versions before 155.0.8059.84, with CVSS 3.1 base score 8.8
- Google released Chrome 155.0.8059.84/.85 (Windows/Mac) and 155.0.8059.84 (Linux) fixing 10 vulnerabilities (1 Critical, 6 High, 3 Medium)
- GBHackers reported the Chrome 155 fixes, noting no exploitation in the wild; staged rollout continues over days to weeks.
- Cyber Security News reported the update, noting Google credits Claude AI assistance for CVE-2026-110913 and reports no exploitation; rollout continues gradually over days to weeks
Update history
- 2026-10-17 — Google Chrome 155 Patches Critical Use-After-Free in Prerender (CVE-2026-110922) and Nine Additional Security Bugs: What changed No field escalation. Severity stays CRITICAL, exploitability stays as published (the report also states no PoC and no in-the-wild exploitation). Additive context only.
Sources cited
- NVD - CVE-2026-110922 NVD (NIST) · Advisory · 2026-10-15
- Chrome Releases - October 2026 (Stable Channel Update for Desktop) chromereleases.googleblog.com · Vendor report · 2026-10-15
- Google Fixes 10 Chrome Vulnerabilities, Including Memory Corruption Flaw Found With Claude AI cybersecuritynews.com · News · 2026-10-17
- Chrome 155 Update Patches 247 Vulnerabilities (SecurityWeek) SecurityWeek · News · 2026-10-07
- Chrome 155 update: 247 security fixes, OpenAI and Anthropic contributions (PiunikaWeb) piunikaweb.com · News · 2026-10-07
- Google Chrome 155: 247 security flaws fixed (IT-Connect) it-connect.fr · News · 2026-10-07
Other reports on CVE-2026-110922
Previous and next in vulnerability
Drafted by the Threadlinqs research pipeline from 6 sources; published ; last updated .