Site isolation bypass via improper print input validation
Published May 28, 2026 · Updated May 28, 2026
Improper input validation in Google Chrome Printing before 148.0.7778.216 allows remote attackers to bypass site isolation via crafted HTML. Google has not disclosed which Printing code path accepts the untrusted data or how its validation fails. Exploitation requires a compromised renderer process and user interaction with the page, enabling that renderer to cross a site-isolation boundary.
Summary
What happened
Improper input validation in Google Chrome Printing before 148.0.7778.216 allows remote attackers to bypass site isolation via crafted HTML. Google has not disclosed which Printing code path accepts the untrusted data or how its validation fails. Exploitation requires a compromised renderer process and user interaction with the page, enabling that renderer to cross a site-isolation boundary.
The record
- CVE
- CVE-2026-9980
- Published
- May 28, 2026
- Updated
- May 28, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-20, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 28, 2026CVE publishedPublication date reported by the CVE source.
- May 28, 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.216 <148.0.7778.216
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.
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