ZeroHour

CVE-2026-93378

mass

Missing-Authorization Storage Flaw Bypasses Site Isolation in Google Chrome PDFs

CVSS 3.1
3.1 low
EPSS
Published
()
Modified
AI analysis

CVE-2026-93378 is a missing-authorization (CWE-862) flaw in the Storage component of Google Chrome, where storage operations fail to properly enforce origin checks. To trigger it, an attacker who has already compromised a renderer process (for example via a chained memory-corruption bug) induces the victim to open a crafted PDF file. Successful exploitation lets the attacker bypass Chrome's site isolation, meaning code in a compromised renderer could potentially access cross-origin data belonging to other sites — a defense-in-depth defeat typically used to escalate a renderer compromise into cross-site data theft. Anyone running Google Chrome before 153.0.8010.52 is affected; the issue is rated Medium by Chromium and was fixed in the Chrome 153.0.8010.52 release, which addressed 16 total flaws including two critical ones. There is no known exploitation, no public proof-of-concept, and the flaw is not listed in CISA KEV.

What to do: Update Google Chrome to 153.0.8010.52 or later immediately (Menu > Help > About Chrome forces the auto-update) and confirm the version at chrome://version. Because exploitation requires an already-compromised renderer, treat this as a chaining target and ensure all renderer/memory-safety fixes from this release are applied as well. No workaround is practical since PDF viewing is built in; rely on prompt patching.

Affected
Google Chromeall versions prior to 153.0.8010.52
Estimated exposure
masson the order of hundreds of millions to billions of installs (Chrome's global desktop base, limited to builds still on pre-153.0.8010.52) — Chrome holds roughly two-thirds of the global browser market (~3 billion-plus users), and because it auto-updates, the affected pool is the share of installs that have not yet received 153.0.8010.52 during the patch rollout window.

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

Description

Missing authorization in Storage in Google Chrome prior to 153.0.8010.52 allowed a remote attacker who had compromised the renderer process to bypass site isolation via a crafted PDF file. (Chromium security severity: Medium)

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

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.