Site isolation bypass via Persistent Cache validation
Published May 6, 2026 · Updated May 6, 2026
Insufficient input validation in Google Chrome before 148.0.7778.96 allows remote attackers to bypass site isolation via crafted HTML. Persistent Cache consumes page-controlled data without sufficient validation; the restricted issue record does not disclose the malformed field or faulty check. Exploitation requires prior renderer compromise and user interaction, and the published impact is limited to cross-site confidentiality exposure.
Summary
What happened
Insufficient input validation in Google Chrome before 148.0.7778.96 allows remote attackers to bypass site isolation via crafted HTML. Persistent Cache consumes page-controlled data without sufficient validation; the restricted issue record does not disclose the malformed field or faulty check. Exploitation requires prior renderer compromise and user interaction, and the published impact is limited to cross-site confidentiality exposure.
The record
- CVE
- CVE-2026-7944
- Published
- May 6, 2026
- Updated
- May 6, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-20, T1068
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 6, 2026CVE publishedPublication date reported by the CVE source.
- May 6, 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=148.0.7778.96 <148.0.7778.96
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