Site isolation bypass via unvalidated extension input
Published Jun 8, 2026 · Updated Jun 8, 2026
Input validation failure in Extensions in Google Chrome before 149.0.7827.103 allows remote attackers to bypass site isolation. The Extensions component insufficiently validates untrusted input from a crafted HTML page, but Google has not disclosed the faulty check or code path. Exploitation requires a compromised renderer process and user interaction with the page; the bounded consequence is a site-isolation bypass.
Summary
What happened
Input validation failure in Extensions in Google Chrome before 149.0.7827.103 allows remote attackers to bypass site isolation. The Extensions component insufficiently validates untrusted input from a crafted HTML page, but Google has not disclosed the faulty check or code path. Exploitation requires a compromised renderer process and user interaction with the page; the bounded consequence is a site-isolation bypass.
The record
- CVE
- CVE-2026-11653
- Published
- Jun 8, 2026
- Updated
- Jun 8, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-20, T1211
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 8, 2026CVE publishedPublication date reported by the CVE source.
- Jun 8, 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.103 <149.0.7827.103
What conditions does exploitation require?
What is affected?
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.
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