Site Isolation bypass via missing Core authorization
Published Sep 9, 2026 · Updated Sep 9, 2026
Missing authorization in Google Chrome Core before 153.0.8010.36 allows remote attackers with a compromised renderer to bypass Site Isolation. Google identifies a missing authorization check in Core but keeps the underlying bug details restricted, so the exact request or state transition is undisclosed. Exploitation requires prior renderer compromise and a crafted HTML page; the bounded result is escape from Site Isolation's cross-site process boundary.
Summary
What happened
Missing authorization in Google Chrome Core before 153.0.8010.36 allows remote attackers with a compromised renderer to bypass Site Isolation. Google identifies a missing authorization check in Core but keeps the underlying bug details restricted, so the exact request or state transition is undisclosed. Exploitation requires prior renderer compromise and a crafted HTML page; the bounded result is escape from Site Isolation's cross-site process boundary.
The record
- CVE
- CVE-2026-87543
- Published
- Sep 9, 2026
- Updated
- Sep 9, 2026
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-862
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 9, 2026CVE publishedPublication date reported by the CVE source.
- Sep 9, 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 versionversion=153.0.8010.36 <153.0.8010.36
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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.
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo