Windows sandbox escape via GPU type confusion
Published Jun 4, 2026 · Updated Jun 4, 2026
Type confusion in Google Chrome's GPU component before 149.0.7827.53 allows remote attackers with renderer control to escape the Windows sandbox. Google identifies the GPU type confusion, but restricted bug details leave the specific object-type mismatch and unsafe operation undisclosed. Exploitation requires a crafted HTML page and prior renderer-process compromise; success crosses the Windows browser sandbox boundary.
Summary
What happened
Type confusion in Google Chrome's GPU component before 149.0.7827.53 allows remote attackers with renderer control to escape the Windows sandbox. Google identifies the GPU type confusion, but restricted bug details leave the specific object-type mismatch and unsafe operation undisclosed. Exploitation requires a crafted HTML page and prior renderer-process compromise; success crosses the Windows browser sandbox boundary.
The record
- CVE
- CVE-2026-11052
- Published
- Jun 4, 2026
- Updated
- Jun 4, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-843, T1203
- 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?
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