Cross-site disclosure via Site Isolation policy bypass
Published Jun 4, 2026 · Updated Jun 4, 2026
Insufficient policy enforcement in Google Chrome before 149.0.7827.53 allows remote attackers to bypass Site Isolation via crafted HTML. The public record names Site Isolation as the faulty policy boundary but does not disclose the code path or policy decision that mishandles the page. Exploitation requires a compromised renderer and user interaction with the crafted page, and the reported consequence is limited to cross-site confidentiality loss.
Summary
What happened
Insufficient policy enforcement in Google Chrome before 149.0.7827.53 allows remote attackers to bypass Site Isolation via crafted HTML. The public record names Site Isolation as the faulty policy boundary but does not disclose the code path or policy decision that mishandles the page. Exploitation requires a compromised renderer and user interaction with the crafted page, and the reported consequence is limited to cross-site confidentiality loss.
The record
- CVE
- CVE-2026-11174
- Published
- Jun 4, 2026
- Updated
- Jun 4, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-693, T1211
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 4, 2026CVE publishedPublication date reported by the CVE source.
- Jun 4, 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=149.0.7827.53 <149.0.7827.53
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.
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