Threat reportVulnerabilityTL-2026-2803
Google Chrome 154 Update Fixes 32 Security Flaws Including Critical ANGLE Buffer Overflow (CVE-2026-102331)
Google released Chrome 154.0.8037.92/.93 (Windows/macOS) and 154.0.8037.92 (Linux), fixing 32 vulnerabilities: one Critical heap buffer overflow in ANGLE (CVE-2026-102331, NVD CVSS 9.6), 25 High, 1 Medium and 5 Low across V8, GPU, WebGPU, WebGL, Dawn, Skia, Mojo and UI components.
Key facts
| Identifiers | TL-2026-2803, CVE-2026-102331, CVE-2026-102317, CVE-2026-102312, CVE-2026-102313, CVE-2026-102299, CVE-2026-102306, CVE-2026-102307, CVE-2026-102323, CVE-2026-102303, CVE-2026-102311, CVE-2026-102300, CVE-2026-102326, CVE-2026-102316, CVE-2026-102304, CVE-2026-102328, CVE-2026-102309, CVE-2026-102325, CVE-2026-102308, CVE-2026-102301, CVE-2026-102319, CVE-2026-102324, CVE-2026-102318, CVE-2026-102329, CVE-2026-102315, CVE-2026-102302, CVE-2026-102321, CVE-2026-102320, CVE-2026-102310, CVE-2026-102327, CVE-2026-102330, CVE-2026-102314, CVE-2026-102305 |
|---|---|
| Also known as | Chrome 154.0.8037.92 security update, Chrome 154 stable channel update (2026-09-29) |
| 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 | |
| EPSS | CVE-2026-102302: 0.3% (26.3th percentile); CVE-2026-102321: 0.3% (25.3th percentile); CVE-2026-102326: 0.3% (23.6th percentile) |
| Affected products | Google Chrome (Windows, macOS, Linux); Google Chrome on Android (per NVD wording for CVE-2026-102331) |
| Weaknesses (CWE) | CWE-122, CWE-416, CWE-843, CWE-908, CWE-787, CWE-125, CWE-79, CWE-862, CWE-863 |
| MITRE ATT&CK techniques | T1059.007 JavaScript, T1203 Exploitation for Client Execution, T1204.001 Malicious Link |
| Motivation | UNKNOWN |
| Target sectors | technology, government administration, finance, health, education, critical-infrastructure |
| Target regions | Global |
| Detection rules | 9 (1 shown free) |
| Sources | 9 cited sources |
Detection coverage
As of 2026-09-30, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-2803 across Splunk SPL, Microsoft KQL and Sigma, covering 15 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: Unpatched Chrome Build Running Before 154.0.8037.92 (CVE-2026-102331 Exposure) — Exploitation
Flags endpoints still executing a Google Chrome build older than 154.0.8037.92 (the first build that fixes the Critical ANGLE heap buffer overflow CVE-2026-102331 and 31 other flaws, including five V8 type confusions). The flaw is reachable by a crafted HTML page (drive-by), so any vulnerable build that is browsing the web is in the exploitable window. Use it to prioritise patching and to scope hosts where other exploitation detections deserve a higher triage priority.
- Languages: Splunk SPL, Microsoft KQL, Sigma
- ATT&CK: T1189, T1203
- Data sources: sysmon, microsoft_defender_for_endpoint
- Severity: medium
- Confidence: high
Splunk SPL
index=sysmon sourcetype="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational" EventCode=1 Image="*\\chrome.exe" FileVersion="*.*.*.*"
``` Parse 154.0.8037.92 style versions and keep anything older than the fixed build ```
| rex field=FileVersion "^(?<v_major>\d+)\.(?<v_minor>\d+)\.(?<v_build>\d+)\.(?<v_rev>\d+)$"
| eval v_major=tonumber(v_major), v_build=tonumber(v_build), v_rev=tonumber(v_rev)
| where v_major<154 OR (v_major==154 AND (v_build<8037 OR (v_build==8037 AND v_rev<92)))
| stats count AS chrome_process_starts, latest(_time) AS last_seen, values(User) AS users, values(Image) AS image_paths BY host, FileVersion
| convert ctime(last_seen)
| sort - chrome_process_startsMicrosoft KQL
DeviceProcessEvents
| where Timestamp > ago(24h)
| where FileName =~ 'chrome.exe' and isnotempty(ProcessVersionInfoProductVersion)
| extend v = split(ProcessVersionInfoProductVersion, '.')
| extend VMajor = toint(v[0]), VBuild = toint(v[2]), VRev = toint(v[3])
| where VMajor < 154 or (VMajor == 154 and (VBuild < 8037 or (VBuild == 8037 and VRev < 92)))
| summarize ProcessStarts = count(), LastSeen = max(Timestamp), Users = make_set(AccountName, 10), Paths = make_set(FolderPath, 5) by DeviceName, ChromeVersion = ProcessVersionInfoProductVersion
| order by ProcessStarts descSigma
title: Vulnerable Google Chrome 154 Build Executed (Pre 154.0.8037.92)
id: 6f1c2a4e-3b7d-4e91-9a52-0c8d1e5b7a01
status: experimental
description: Detects execution of Google Chrome builds known to be vulnerable to CVE-2026-102331 (ANGLE heap buffer overflow) and the 31 other flaws fixed in 154.0.8037.92/.93. Sigma cannot compare version numbers, so known vulnerable 154.0.8037.57/.58 builds and any 153.x build are matched; use the SPL/KQL forms for full numeric comparison.
references:
- https://chromereleases.googleblog.com/2026/09/stable-channel-update-for-desktop_01807488085.html
- https://nvd.nist.gov/vuln/detail/CVE-2026-102331
author: Threadlinqs Team
date: 2026-09-30
tags:
- attack.initial-access
- attack.t1189
- attack.execution
- attack.t1203
- cve.2026-102331
logsource:
category: process_creation
product: windows
detection:
selection_img:
Image|endswith: '\chrome.exe'
selection_version:
FileVersion|startswith:
- '154.0.8037.57'
- '154.0.8037.58'
- '153.'
condition: selection_img and selection_version
falsepositives:
- Hosts awaiting a scheduled browser relaunch after an update has been staged
- Golden images or VDI templates that are not yet patched
level: mediumKnown false positives:
- Endpoints that have downloaded 154.0.8037.92 but not yet relaunched Chrome still report the old running version
- Unmanaged or portable Chrome installs on lab machines that are intentionally pinned
Tuning notes: Windows/macOS fixed build is 154.0.8037.92/.93 and Linux is .92; the thresholds use .92 so a .92 Windows host is not alerted. Join with asset inventory to prioritise admins, developers and internet-facing kiosks, and suppress hosts with a pending RelaunchNotification period. Sysmon FileVersion is empty on some installs; fall back to the Defender ProcessVersionInfoProductVersion form.
- Chrome Crash in ANGLE/GPU Graphics Modules (Possible Exploit Attempt) — Exploitation · unlock with TL Creds
- Sandboxed Chrome Renderer/GPU Process Spawning a Child — Sandbox Escape · unlock with TL Creds
- Outbound Public Connections From Chrome-Spawned Non-Browser Process — C2 · unlock with TL Creds
- Chrome Launched With URL From Office/Mail/Script Host or With javascript:/data: URL — Delivery · unlock with TL Creds
- Chrome Started With Sandbox or Site-Isolation Protections Disabled — Sandbox Weakening · unlock with TL Creds
- Chrome Process Writing Executable or Script to Startup/Staging Location — Payload Drop and Persistence · unlock with TL Creds
- Chrome Spawning Shell or LOLBin Child Process — Post-Exploitation · unlock with TL Creds
- Download Cradle Launched From Chrome Process Tree — C2 / Ingress Tool Transfer · unlock with TL Creds
Indicators of compromise
As of 2026-09-30, Threadlinqs Intelligence tracks 15 indicators of compromise for TL-2026-2803.
Sample indicators (2 of 15)
- URL:
hxxps://chromereleases[.]googleblog[.]com/2026/09/stable-channel-update-for-desktop_01807488085.html - URL:
hxxps://issues[.]chromium[.]org/issues/551673541
Defanged, TLP:CLEAR. Full set of 15 indicators: unlock with TL Creds.
Technical analysis
No active exploitation has been reported and the CVEs are not in CISA KEV.
Google's Stable Channel Update for Desktop published on 2026-09-29 (reported by GBHackers on 2026-09-30) ships Chrome 154.0.8037.92/.93 for Windows and macOS and 154.0.8037.92 for Linux. It fixes 32 security issues: 1 Critical, 25 High, 1 Medium and 5 Low. This is a follow-up point release to the initial Chrome 154 stable build 154.0.8037.57/.58 of 2026-09-22, which fixed 108 flaws.
The Critical issue, CVE-2026-102331, is a buffer overflow in ANGLE, Chrome's graphics translation layer that maps WebGL/OpenGL ES calls onto native graphics APIs. The reporter is @mfx. NVD records it as CWE-122 (heap-based buffer overflow) with a CVSS 3.1 base score of 9.6 (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H), currently 'Awaiting Analysis'. The NVD description says a remote attacker could potentially execute arbitrary code outside the sandbox via a crafted HTML page. That text says 'Chrome on Android prior to 154.0.8037.92', while the desktop release notes list the same build number, so platform scope should be confirmed against the Chromium issue (551673541). Google has withheld technical details and no exploit scenario or PoC is public.
The 25 High-severity fixes are dominated by memory-safety and uninitialized-resource bugs. V8 has five type confusions (CVE-2026-102299, -102321, and three found by OpenAI Codex Security: -102323, -102326, -102328) and one buffer overflow (-102302). GPU, WebGPU, Dawn, Skia, ANGLE and Media have uninitialized-resource bugs (-102303, -102311, -102319, -102300, -102307, -102325, -102313, -102315). GPU has an out-of-bounds write (-102301) and WebGL an out-of-bounds read (-102318). Use-after-free bugs affect Bluetooth (-102306), Views (-102316, -102308), Passwords (-102304), FullScreen (-102309) and Picture-in-Picture (-102324). The rest are Mojo privilege mismanagement (-102317), Omnibox UI misrepresentation (-102312) and WebUI cross-site scripting (-102329). The Medium/Low group is authorization and UI-spoofing issues in CORS (-102320, Medium), Payments (-102310), WebView (-102327), Site Isolation (-102330), TabStrip (-102314) and SignIn (-102305).
Google has not indicated exploitation in the wild, and none of CVE-2026-102299 through CVE-2026-102331 appear in the CISA KEV catalog checked on 2026-09-30. Chrome V8 bugs CVE-2026-85046 and CVE-2026-87491 were added to KEV earlier in September 2026, so the browser engine remains an actively targeted surface. Because renderer, GPU and ANGLE memory-corruption bugs are typically chained with sandbox escapes once details are released, patch-gap risk rises after disclosure. Defenders should push the update to all Chromium-based browsers as downstream vendors ship it.
MITRE ATT&CK techniques by tactic:
Execution
T1059.007 JavaScript; T1203 Exploitation for Client Execution; T1204.001 Malicious Link
Remediation
Patches
- Chrome 154.0.8037.92/.93 Windows and macOS
- Chrome 154.0.8037.92 Linux
Immediate actions
- Update Google Chrome to 154.0.8037.92 (Linux) or 154.0.8037.92/.93 (Windows/macOS) or later, then relaunch the browser
- Verify the version at chrome://settings/help across the managed fleet
- Prioritise internet-facing and high-risk user endpoints (admins, developers, executives)
Workarounds
- No vendor workaround published; where patching is delayed, restrict browsing to trusted sites and consider disabling hardware acceleration/WebGL for high-risk users as a temporary risk reduction
Longer-term hardening
- Enforce browser auto-update and a short relaunch deadline via enterprise policy (RelaunchNotification / RelaunchNotificationPeriod)
- Track downstream Chromium-based browsers (Edge, Brave, Opera, Vivaldi) and Electron apps for equivalent fixes
- Keep Chrome site isolation and the renderer sandbox enabled; do not run with --no-sandbox
Affected and fixed versions
- Google — Chrome (Windows, macOS, Linux)
Vulnerable versions: prior to 154.0.8037.92 (Linux); prior to 154.0.8037.92/.93 (Windows/macOS)
Fixed in: 154.0.8037.92 (Linux); 154.0.8037.92/.93 (Windows/macOS) - Google — Chrome on Android (per NVD wording for CVE-2026-102331)
Vulnerable versions: prior to 154.0.8037.92
Fixed in: 154.0.8037.92
Timeline
- CISA adds Chrome V8 type-confusion CVE-2026-85046 to KEV, showing the browser engine is an actively exploited surface earlier in the month
- CISA adds Chrome V8 out-of-bounds write CVE-2026-87491 to KEV (remediation due 2026-09-23)
- Chrome 154 stable ships as 154.0.8037.57/.58 with 108 security fixes, including 11 Critical (per PCWorld/Malwarebytes reporting)
- Google publishes the Stable Channel Update for Desktop on the Chrome Releases blog with builds 154.0.8037.92/.93 (Windows/macOS) and 154.0.8037.92 (Linux)
- None of CVE-2026-102299 to CVE-2026-102331 is present in the CISA KEV catalog; no in-the-wild exploitation reported
- NVD publishes CVE-2026-102331 (CWE-122, CVSS 3.1 9.6) with status Awaiting Analysis; Chromium issue 551673541 referenced
- GBHackers reports 32 security fixes: 1 Critical (ANGLE CVE-2026-102331), 25 High, 1 Medium, 5 Low; Google withholds technical details until most users update
Sources cited
- NVD: CVE-2026-102331 NVD (NIST) · Advisory · 2026-09-30
- CISA Known Exploited Vulnerabilities Catalog CISA · Government advisory · 2026-09-30
- Chrome Releases: Stable Channel Update for Desktop (154.0.8037.92) chromereleases.googleblog.com · Vendor report · 2026-09-29
- Chromium issue 551673541 (CVE-2026-102331) issues.chromium.org · Vendor report · 2026-09-30
- Chrome Releases blog (September 2026 archive) chromereleases.googleblog.com · Vendor report · 2026-09-29
- Update Chrome: 108 security fixes for desktop (Malwarebytes) malwarebytes.com · Blog · 2026-09-22
- Google Chrome 154 Update Fixes 32 Security Flaws Including Critical ANGLE Bug (GBHackers) gbhackers.com · News · 2026-09-30
- Chrome 154 fixes 108 security flaws including 11 critical bugs (PCWorld) pcworld.com · News · 2026-09-22
- Google Chrome 154 Fixes 108 Security Flaws: What IT Teams Should Check (eSecurity Planet) esecurityplanet.com · News · 2026-09-22
Previous and next in vulnerability
Drafted by the Threadlinqs research pipeline from 9 sources; published ; last updated —.