Site-isolation bypass via faulty ORB authorization
Published Sep 17, 2026 · Updated Sep 17, 2026
Incorrect authorization in ORB in Google Chrome before 153.0.8010.52 allows remote attackers to bypass site isolation via crafted HTML. Google identifies ORB as the affected component but has not disclosed the failing authorization check or code path. A user must open the crafted page; the documented impact is limited to the browser isolation boundary, with no reported code execution.
Summary
What happened
Incorrect authorization in ORB in Google Chrome before 153.0.8010.52 allows remote attackers to bypass site isolation via crafted HTML. Google identifies ORB as the affected component but has not disclosed the failing authorization check or code path. A user must open the crafted page; the documented impact is limited to the browser isolation boundary, with no reported code execution.
The record
- CVE
- CVE-2026-93379
- Published
- Sep 17, 2026
- Updated
- Sep 17, 2026
- Vendor
- WebM Project
- Product
- Chrome
- Classifications
- CWE-863
- 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