Site isolation bypass via flawed CORS enforcement
Published Aug 18, 2026 · Updated Aug 19, 2026
Site isolation bypass in Chrome before 151.0.7922.169 allows remote attackers with a compromised renderer to access cross-site data via HTML. Public advisories identify Chrome's CORS handling as the failing component, but the specific check or code path that mishandles untrusted cross-origin responses remains undisclosed. Exploitation requires prior compromise of the renderer process, so the bug is most relevant as a second-stage browser boundary bypass that can expose data from other sites.
Summary
What happened
Site isolation bypass in Chrome before 151.0.7922.169 allows remote attackers with a compromised renderer to access cross-site data via HTML. Public advisories identify Chrome's CORS handling as the failing component, but the specific check or code path that mishandles untrusted cross-origin responses remains undisclosed. Exploitation requires prior compromise of the renderer process, so the bug is most relevant as a second-stage browser boundary bypass that can expose data from other sites.
The record
- CVE
- CVE-2026-76033
- Published
- Aug 18, 2026
- Updated
- Aug 19, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-20, CWE-653
- Attack vector
- network
- Privileges
- Unavailable
Timeline
How it unfolded
- Aug 18, 2026CVE publishedPublication date reported by the CVE source.
- Aug 19, 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=151.0.7922.169 <151.0.7922.169
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