Sandbox escape via unvalidated printing input
Published Jun 4, 2026 · Updated Jun 4, 2026
Input validation failure in Chrome Printing before 149.0.7827.53 allows remote attackers to escape the renderer sandbox on Windows. The public record identifies crafted HTML as the input but does not disclose the Printing code path or the validation operation that mishandles it. Exploitation requires a crafted page and prior renderer-process compromise; success crosses the sandbox boundary and exposes the host process context.
Summary
What happened
Input validation failure in Chrome Printing before 149.0.7827.53 allows remote attackers to escape the renderer sandbox on Windows. The public record identifies crafted HTML as the input but does not disclose the Printing code path or the validation operation that mishandles it. Exploitation requires a crafted page and prior renderer-process compromise; success crosses the sandbox boundary and exposes the host process context.
The record
- CVE
- CVE-2026-10971
- Published
- Jun 4, 2026
- Updated
- Jun 4, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-20, T1068
- 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?
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