Skip to navigation

Threat reportVulnerabilityTL-2026-1770

Google Chrome 151 (151.0.7922.71/.72) Patches 370 Security Flaws Including 7 Critical Sandbox-Escape / Local-Privilege-Escalation Bugs (CVE-2026-17650 – CVE-2026-17656)

criticalPATCHED

Google's July 29-30, 2026 Chrome 151 stable channel update (151.0.7922.71/.72 Windows/macOS, 151.0.7922.71 Linux) fixes 370 security issues -- 7 critical, 71 high, 170 medium, 122 low.

Key facts

IdentifiersTL-2026-1770, CVE-2026-17650, CVE-2026-17651, CVE-2026-17652, CVE-2026-17653, CVE-2026-17654, CVE-2026-17655, CVE-2026-17656
SeverityCRITICAL
EPSSCVE-2026-17655: 0.5% (44.1th percentile); CVE-2026-17653: 0.4% (39.9th percentile); CVE-2026-17651: 0.3% (25.9th percentile)
Affected productsGoogle Google Chrome (Windows); Google Google Chrome (macOS); Google Google Chrome (Linux); Google Google Chrome (Android); Google / Chromium Project Chromium (open-source upstream; affects all downstream Chromium-based browsers pending their own rebase)
Weaknesses (CWE)CWE-416, CWE-20, CWE-362
ToolsAFL, AddressSanitizer, Control Flow Integrity, MemorySanitizer, UndefinedBehaviorSanitizer, libFuzzer
MITRE ATT&CK techniquesT1059.007 JavaScript, T1068 Exploitation for Privilege Escalation, T1082 System Information Discovery, T1189 Drive-by Compromise, T1203 Exploitation for Client Execution, T1204.001 Malicious Link, T1204.002 Malicious File, T1211 Exploitation for Stealth, T1548 Abuse Elevation Control Mechanism, T1566.002 Spearphishing Link, T1574.010 Services File Permissions Weakness, T1587.004 Exploits and 4 more in the attack flow
MotivationUNKNOWN
Target sectorsgovernment administration, finance, health, technology, education, critical-infrastructure, retail, general-enterprise
Target regionsglobal
Detection rules9 (1 shown free)
Sources17 cited sources

Detection coverage

As of 2026-07-30, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-1770 across Splunk SPL, Microsoft KQL and Sigma, covering 29 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: Post-Escape Persistence Write Correlated With Updater File-Race (TOCTOU) — CVE-2026-17654 + Post-Escape Persistence (SPL)

Detects a Run-key/LaunchAgent persistence artifact created by chrome.exe or one of its recently-spawned children within a short window of a sandbox-escape process-tree event, OR repeated sub-second rewrites (differing content hash) of a Chrome Updater/installer payload path — the file-race signature of CVE-2026-17654 (race condition in the Chrome Updater, macOS, CWE-362) in which a LOCAL attacker swaps a malicious file between the Updater's permission check and its privileged install step to achieve OS-level privilege escalation, and the persistence an attacker is likely to plant once that higher-privileged context is obtained.

  • Languages: Splunk SPL, Microsoft KQL, Sigma
  • ATT&CK: T1547.001, T1574.010, T1548, T1068
  • Data sources: sysmon, windows_registry, osquery, macos_unified_logs
  • Severity: high
  • Confidence: medium

Splunk SPL

(index=sysmon sourcetype="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational" EventCode=13
  TargetObject="*\\Software\\Microsoft\\Windows\\CurrentVersion\\Run\\*"
  (Image="*\\chrome.exe" OR Image="*\\cmd.exe" OR Image="*\\powershell.exe")
 | table _time, host, user, Image, TargetObject, Details)
APPEND
[search index=osquery sourcetype="osquery:results" table_name=file_events
  (target_path="*/Library/LaunchAgents/*.plist" OR target_path="*/Library/LaunchDaemons/*.plist")
  (action="created" OR action="updated")
 | table _time, host, columns.username as user, target_path]
APPEND
[search index=osquery sourcetype="osquery:results" table_name=file_events
  (target_path="*GoogleSoftwareUpdate*" OR target_path="*ksinstall*" OR target_path="*update_payload*" OR target_path="*installer*")
 | bin _time span=1s
 | stats count dc(md5) as distinct_hashes values(target_path) as target_path by host, _time
 | where count>1 AND distinct_hashes>1]
| sort - _time

Microsoft KQL

let PersistWindow = 5m;
let SuspiciousParent = DeviceProcessEvents
| where Timestamp > ago(24h)
| where InitiatingProcessFileName =~ "chrome.exe"
| where FileName in~ ("cmd.exe","powershell.exe")
| project ParentTs = Timestamp, DeviceName;
DeviceRegistryEvents
| where Timestamp > ago(24h)
| where RegistryKey has @"CurrentVersion\Run"
| where InitiatingProcessFileName in~ ("chrome.exe","cmd.exe","powershell.exe")
| join kind=inner (SuspiciousParent) on DeviceName
| where Timestamp between (ParentTs .. ParentTs + PersistWindow)
| project Timestamp, DeviceName, InitiatingProcessFileName, Artifact = RegistryKey, ArtifactDetail = RegistryValueData
| union (
    DeviceFileEvents
    | where Timestamp > ago(24h)
    | where FolderPath has_any ("LaunchAgents","LaunchDaemons") and FileName endswith ".plist"
    | project Timestamp, DeviceName, InitiatingProcessFileName, Artifact = FolderPath, ArtifactDetail = FileName
  )
| union (
    DeviceFileEvents
    | where Timestamp > ago(24h)
    | where FileName has_any ("GoogleSoftwareUpdate","ksinstall","update_payload","installer")
    | summarize EventCount = count(), DistinctHashes = dcount(SHA256) by DeviceName, FolderPath, bin(Timestamp, 1s)
    | where EventCount > 1 and DistinctHashes > 1
    | project Timestamp, DeviceName, InitiatingProcessFileName = "(file-race)", Artifact = FolderPath, ArtifactDetail = strcat("race window, distinct hashes=", DistinctHashes)
  )

Sigma

title: Persistence Key or LaunchAgent Created Near Browser-Initiated Child Process, or Updater Payload File Race (TOCTOU)
id: 5b6c7d8e-9f0a-4b1c-8d2e-3f4a5b6c7d8e
status: experimental
description: Detects a Run-key/LaunchAgent persistence write by chrome.exe or a chrome-spawned child shortly after an unexplained child-process event, and/or repeated sub-second rewrites of a Chrome Updater/installer payload path -- the TOCTOU file-race signature of CVE-2026-17654 (Chrome Updater race condition, macOS, CWE-362) and the persistence an attacker plants after winning that race for OS-level privilege escalation.
references:
    - https://gbhackers.com/google-chrome-151-fixes-370-security-flaws/
    - https://nvd.nist.gov/vuln/detail/CVE-2026-17654
author: Threadlinqs Team
date: 2026-07-30
tags:
    - attack.persistence
    - attack.t1547.001
    - attack.privilege-escalation
    - attack.t1574.010
    - attack.t1548
    - attack.t1068
    - cve.2026.17654
logsource:
    product: windows
    category: registry_add
detection:
    selection:
        TargetObject|contains: '\Software\Microsoft\Windows\CurrentVersion\Run\'
        Image|endswith:
            - '\chrome.exe'
            - '\cmd.exe'
            - '\powershell.exe'
    condition: selection
falsepositives:
    - Legitimate Chrome-managed extensions/update helpers writing Run keys or LaunchAgents (rare)
    - IT deployment tools that legitimately rewrite installer/updater payloads multiple times during staged rollout
level: medium

Known false positives:

  • Legitimate Chrome-managed extensions/update helpers writing Run keys or LaunchAgents (rare)
  • IT deployment tools that legitimately rewrite installer/updater payloads multiple times during staged rollout

Tuning notes: Narrow the persistence-correlation window (default 5m) to your environment's observed dwell time between escape and persistence; for the file-race clause, tune the sub-second bin span and hash-diversity threshold against your update-tooling's normal atomic-write behavior (rename-based updaters won't trigger this) to avoid flagging benign staged-rollout retries.

8 more detection rules (Splunk SPL, Microsoft KQL, Sigma) · unlock with TL Creds. Sign up free to unlock the detection rules or query them with the Threadlinqs MCP server (Purple)
  • Chrome Renderer Spawning Unexpected Child Process — Sandbox-Escape Signature (KQL) · unlock with TL Creds
  • Post-Escape Persistence Write Correlated With Updater File-Race (TOCTOU) — CVE-2026-17654 + Post-Escape Persistence (KQL) · unlock with TL Creds
  • Chrome Outbound Callback Following Anomalous Child-Process Spawn — Post-Escape C2 Candidate (KQL) · unlock with TL Creds
  • Chrome Renderer Spawning Unexpected Child Process — Sandbox-Escape Signature (Sigma) · unlock with TL Creds
  • Post-Escape Persistence Write Correlated With Updater File-Race (TOCTOU) — CVE-2026-17654 + Post-Escape Persistence (Sigma) · unlock with TL Creds
  • Chrome Outbound Callback Following Anomalous Child-Process Spawn — Post-Escape C2 Candidate (Sigma) · unlock with TL Creds
  • Chrome Renderer Spawning Unexpected Child Process — Sandbox-Escape Signature (SPL) · unlock with TL Creds
  • Chrome Outbound Callback Following Anomalous Child-Process Spawn — Post-Escape C2 Candidate (SPL) · unlock with TL Creds

Indicators of compromise

As of 2026-07-30, Threadlinqs Intelligence tracks 29 indicators of compromise for TL-2026-1770.

29 indicators of compromise · unlock with TL Creds. Compare plans

Technical analysis

All 7 critical bugs are confirmed via NVD: four use-after-free flaws (Compositing, Views, Skia, Ozone) and two insufficient-input-validation flaws (Dawn/WebGPU on Android, ANGLE) that enable sandbox escape once a renderer process is already compromised via a crafted HTML page, plus a race condition in the Chrome Updater on macOS enabling local OS-level privilege escalation via a malicious file. No CVE in this batch appears in the CISA KEV catalog and no public PoC or in-the-wild exploitation has been reported.

On July 29-30, 2026, Google published the Chrome 151 stable channel update (chromereleases.googleblog.com), raising the desktop build to 151.0.7922.71/.72 on Windows and macOS and 151.0.7922.71 on Linux, and fixing 370 total security issues (7 critical / 71 high / 170 medium / 122 low per the GBHackers writeup that seeded this threat). The 7 critical issues were independently confirmed against NVD, each carrying a Chromium 'Critical' severity rating and a linked issues.chromium.org tracker entry (still access-restricted, consistent with Google's standard embargo until a majority of users have updated):

- CVE-2026-17650 -- Use-after-free in Compositing (CWE-416): a remote attacker who has already compromised the renderer process can potentially achieve sandbox escape via a crafted HTML page. - CVE-2026-17651 -- Insufficient validation of untrusted input in Dawn (Chrome's WebGPU implementation) on Android (CWE-20): a remote attacker can potentially perform sandbox escape via a crafted HTML page. This is the only one of the seven scoped specifically to Android. - CVE-2026-17652 -- Use-after-free in Views, Chromium's cross-platform UI toolkit (CWE-416): same renderer-compromise-to-sandbox-escape pattern as 17650. - CVE-2026-17653 -- Use-after-free in Skia, Chromium's 2D graphics rendering library (CWE-416): same pattern. - CVE-2026-17654 -- Race condition in the Chrome Updater on macOS (CWE-362): a LOCAL attacker can perform OS-level privilege escalation via a malicious file. This is the only one of the seven that does not require a prior renderer compromise and does not rely on the 'crafted HTML page' vector -- it is a local, file-based TOCTOU-class updater flaw. - CVE-2026-17655 -- Insufficient validation of untrusted input in ANGLE, the graphics translation layer Chrome uses to map WebGL/GPU calls to native graphics APIs (CWE-20): sandbox escape via crafted HTML page. - CVE-2026-17656 -- Use-after-free in Ozone, Chromium's Linux/embedded display-abstraction layer (CWE-416): sandbox escape via crafted HTML page.

Six of the seven (all except the Updater race condition) follow an identical exploit-chain shape documented verbatim in each NVD record: the attacker must first achieve arbitrary code execution inside the sandboxed renderer process (typically via a separate, unpatched renderer-side memory-corruption bug or a scripting-engine flaw, not part of this disclosure), and then trigger the UAF/validation flaw in a lower-privileged-but-still-sandboxed component (Compositing, Views, Skia, Ozone, Dawn, ANGLE) to break out of the Chrome sandbox into the higher-privileged browser process -- i.e., these are second-stage sandbox-escape primitives in a multi-bug exploit chain, not standalone remote-code-execution bugs on their own. This matches the classic Chrome exploit-chain pattern (renderer 1-day/0-day + sandbox-escape 1-day/0-day) used by commercial exploit brokers and APT-affiliated exploit developers.

Google credited a mix of external researchers and internal detection via memory-safety tooling (AddressSanitizer, MemorySanitizer, UndefinedBehaviorSanitizer, Control Flow Integrity, libFuzzer, and AFL fuzzing) for the broader 370-bug batch; the source article did not break out individual bounty amounts or named researchers for the 7 critical bugs specifically. Neither the GBHackers source article, the Chrome release blog excerpt, nor a direct CISA KEV catalog check found evidence of active exploitation or a public proof-of-concept for any of the 7 critical CVEs as of 2026-07-30. Given Chrome's dominant global browser market share, the volume of critical memory-safety fixes in a single release, and the fact 6 of 7 are sandbox-escape primitives exploitable via nothing more than a crafted web page (once chained with a renderer bug), this release warrants priority patch rollout even absent confirmed in-the-wild activity.

MITRE ATT&CK techniques by tactic:

Execution

T1059.007 JavaScript; T1203 Exploitation for Client Execution; T1204.001 Malicious Link; T1204.002 Malicious File

Privilege Escalation

T1068 Exploitation for Privilege Escalation; T1548 Abuse Elevation Control Mechanism

Discovery

T1082 System Information Discovery

Initial Access

T1189 Drive-by Compromise; T1566.002 Spearphishing Link

Defense Evasion

T1211 Exploitation for Stealth

stealth

T1574.010 Services File Permissions Weakness

Resource Development

T1587.004 Exploits; T1588.005 Exploits; T1588.006 Vulnerabilities; T1608.005 Link Target

Reconnaissance

T1592.002 Software

Remediation

Patches

  • Google Chrome 151.0.7922.71/.72 (Windows)
  • Google Chrome 151.0.7922.71/.72 (macOS)
  • Google Chrome 151.0.7922.71 (Linux)
  • Google Chrome 151.0.7922.72 (Android, for CVE-2026-17651)

Immediate actions

  • Update Google Chrome to 151.0.7922.71/.72 (Windows), 151.0.7922.71/.72 (macOS), or 151.0.7922.71 (Linux) via chrome://settings/help, then relaunch the browser to load the patched binary.
  • For managed/enterprise fleets, push the update via Chrome Enterprise policy (TargetVersionPrefix / auto-update) rather than waiting on end-user relaunch, given 6 of the 7 critical bugs are exploitable via nothing more than visiting a crafted web page once chained with a renderer bug.
  • macOS fleets specifically: prioritize rollout given CVE-2026-17654 is a locally-triggerable Updater race condition unique to macOS.
  • Android fleets: prioritize rollout given CVE-2026-17651 (Dawn/WebGPU) is Android-specific.

Workarounds

  • No official workaround supersedes patching. Disabling WebGPU (chrome://flags -> #enable-unsafe-webgpu / Dawn) reduces exposure to CVE-2026-17651 on Android until patched.
  • Disabling GPU/hardware compositing (chrome://flags -> #disable-gpu-compositing) offers partial mitigation for the Compositing UAF (CVE-2026-17650) but degrades rendering performance and is not a substitute for updating.

Longer-term hardening

  • Enforce mandatory automatic browser updates via Chrome Enterprise / Chrome Browser Cloud Management so critical patches land within days, not weeks.
  • Maintain Site Isolation and renderer-sandbox hardening as defense-in-depth against the class of UAF/sandbox-escape bugs recurring across Compositing, Views, Skia, Ozone, Dawn, and ANGLE.
  • Track the CVE-2026-17650 through CVE-2026-17656 range against fleet telemetry (chrome://version reporting) to confirm 100% patch compliance, and re-check CISA KEV periodically in case any of the seven are later added following in-the-wild observation.

Affected and fixed versions

  • Google — Google Chrome (Windows)
    Vulnerable versions: < 151.0.7922.71
    Fixed in: 151.0.7922.71; 151.0.7922.72
  • Google — Google Chrome (macOS)
    Vulnerable versions: < 151.0.7922.71
    Fixed in: 151.0.7922.71; 151.0.7922.72
  • Google — Google Chrome (Linux)
    Vulnerable versions: < 151.0.7922.71
    Fixed in: 151.0.7922.71
  • Google — Google Chrome (Android)
    Vulnerable versions: < 151.0.7922.72
    Fixed in: 151.0.7922.72
  • Google / Chromium Project — Chromium (open-source upstream; affects all downstream Chromium-based browsers pending their own rebase)
    Vulnerable versions: < 151.0.7922.71
    Fixed in: 151.0.7922.71+

Timeline

  • Google publishes the Chrome 151 Stable Channel Update for Desktop blog post, raising the build to 151.0.7922.71/.72 (Windows/macOS) and 151.0.7922.71 (Linux) and fixing 370 total security issues.
  • CISA Known Exploited Vulnerabilities catalog checked directly; none of CVE-2026-17650 through CVE-2026-17656 present, confirming no CISA-confirmed active exploitation as of this analysis.
  • TL-Intel-Harness ingests the GBHackers article via the RSS hunt pipeline and opens threat TL-2026-1770.
  • GBHackers publishes "Google Chrome 151 Fixes 370 Security Flaws", summarizing all severity tiers and the 7 critical component-level bugs.
  • CVE-2026-17656 (use-after-free in Ozone, Chromium issue #523725277) published in NVD as Critical severity.
  • CVE-2026-17655 (insufficient validation in ANGLE, Chromium issue #522556145) published in NVD as Critical severity.
  • CVE-2026-17654 (race condition in Chrome Updater on macOS, Chromium issue #522314940) published in NVD as Critical severity -- the only bug in the batch enabling local OS-level privilege escalation via a malicious file rather than sandbox escape via a web page.
  • CVE-2026-17653 (use-after-free in Skia, Chromium issue #520514458) published in NVD as Critical severity.
  • CVE-2026-17652 (use-after-free in Views, Chromium issue #519262990) published in NVD as Critical severity.
  • CVE-2026-17651 (insufficient validation in Dawn/WebGPU on Android, Chromium issue #517307966) published in NVD as Critical severity.
  • CVE-2026-17650 (use-after-free in Compositing, Chromium issue #514442821) published in NVD as Critical severity.

Sources cited

Showing 15 of 17 sources, primary sources first.

Previous and next in vulnerability

Drafted by the Threadlinqs research pipeline from 17 sources; published ; last updated —.

Threadlinqs Intelligence — Real-Time Threat Detection Platform

// threat_feed
$ sort --newest
Showing all threats

Live intelligence console

Threat level

Latest Threats