ZeroHour

CVE-2026-93375

mass

Incorrect Reference Resolution in Chrome Tracing Enables Local Sandbox Escape on Windows

CVSS 3.1
8.1 high
EPSS
Published
()
Modified
AI analysis

CVE-2026-93375 is an incorrect reference resolution flaw (CWE-706) in the Tracing component of Google Chrome on Windows. A local attacker who can already run a program on the machine can abuse the flaw to potentially execute arbitrary code outside the Chrome sandbox, meaning code escapes the browser's process-isolation boundary. Successful exploitation typically serves as a sandbox escape that can be chained with other browser flaws for fuller system compromise. Only Chrome on Windows prior to 153.0.8010.52 is affected; the fix shipped in the Chrome 153.0.8010.52 release, which addressed 16 security issues including two critical ones. No public proof-of-concept is known, the issue is not on the CISA KEV list, and no in-the-wild exploitation has been confirmed.

What to do: Update Google Chrome on Windows to version 153.0.8010.52 or later immediately (via Settings > About Chrome or your enterprise update channel) and verify the version at chrome://version. Because exploitation requires a local program, prioritize patching shared, multi-user, and kiosk-style Windows systems where local code execution by untrusted users is more likely. No mitigation short of upgrading is published; restrict local program execution on sensitive machines in the interim.

Affected
Google Chrome (Windows)prior to 153.0.8010.52
Estimated exposure
mass≈1–3 billion Chrome-on-Windows installations (Chrome holds roughly two-thirds of desktop browser share) — Chrome is the dominant desktop browser globally with an estimated multi-billion-user install base, and Windows is the majority desktop platform, so the number of Chrome-on-Windows instances plausibly affected is well over one million; note…

Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.

Description

Incorrect reference resolution in Tracing in Google Chrome on on Windows prior to 153.0.8010.52 allowed a local attacker to potentially execute arbitrary code outside the sandbox via a local program. (Chromium security severity: High)

Weakness
CWE-706
Vector
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H

In the news

Google Chrome 153 Update Fixes 16 Security Flaws, Including Two Critical Vulnerabilities

Google released Chrome 153 fixing 16 vulnerabilities, including critical use-after-free in Dawn/WebGPU and a WebGL buffer overflow, across Windows, macOS, and Linux.

Chrome 153.0.8010.52 for the Stable desktop channel patches 16 flaws, including critical CVE-2026-93374, a use-after-free in Dawn (Chromium's WebGPU implementation), and critical CVE-2026-93372, a WebGL buffer overflow. High-severity fixes cover use-after-free and buffer overflow bugs in PDFium, incorrect state validation in Skia, a use-after-free in Extensions, incorrect authorization in ORB, and type confusion in V8. Google restricts technical exploit details until most users have updated; a browser restart is required to activate the patch.

Chrome 153 Patches 16 Security Vulnerabilities Including Critical Dawn and WebGL Flaws

Google released Chrome 153 fixing 16 flaws, including critical use-after-free in Dawn (CVE-2026-93374) and buffer overflow in WebGL (CVE-2026-93372).

Google shipped Chrome 153.0.8010.52/.53 for Windows, macOS, and Linux, patching 16 vulnerabilities: 2 critical, 8 high, 5 medium, and 1 low. The critical flaws are a use-after-free in Dawn, Chrome's WebGPU implementation (CVE-2026-93374), and a WebGL buffer overflow (CVE-2026-93372). High-severity fixes include a V8 type confusion (CVE-2026-93377), two PDFium bugs, and issues in Skia, Extensions, ORB, and Tracing. No exploitation is reported; Google is withholding technical details until most users have updated.