Site isolation bypass via Storage authorization failure
Published Sep 17, 2026 · Updated Sep 17, 2026
Missing authorization in Google Chrome Storage before 153.0.8010.52 allows remote attackers to bypass site isolation through a crafted PDF. Google identifies Storage as the faulty component but has not disclosed the specific operation or authorization check that accepts the PDF. Exploitation requires a separately compromised renderer and user interaction with the PDF; the reported consequence is a site isolation bypass, not host code execution.
Summary
What happened
Missing authorization in Google Chrome Storage before 153.0.8010.52 allows remote attackers to bypass site isolation through a crafted PDF. Google identifies Storage as the faulty component but has not disclosed the specific operation or authorization check that accepts the PDF. Exploitation requires a separately compromised renderer and user interaction with the PDF; the reported consequence is a site isolation bypass, not host code execution.
The record
- CVE
- CVE-2026-93378
- Published
- Sep 17, 2026
- Updated
- Sep 17, 2026
- Vendor
- WebM Project
- Product
- Chrome
- Classifications
- CWE-862
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 17, 2026CVE publishedPublication date reported by the CVE source.
- Sep 17, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected version<153.0.8010.52
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started