Sandbox escape via GPU heap buffer overflow
Published Jun 11, 2026 · Updated Jun 11, 2026
Heap buffer overflow in Google Chrome before 149.0.7827.115 allows remote attackers to escape the sandbox through crafted HTML. Google identifies the GPU component but has not published the faulty allocation or bounds operation because the linked issue remains access-restricted. Exploitation requires a compromised renderer process and interaction with crafted HTML, and success breaks the renderer sandbox.
Summary
What happened
Heap buffer overflow in Google Chrome before 149.0.7827.115 allows remote attackers to escape the sandbox through crafted HTML. Google identifies the GPU component but has not published the faulty allocation or bounds operation because the linked issue remains access-restricted. Exploitation requires a compromised renderer process and interaction with crafted HTML, and success breaks the renderer sandbox.
The record
- CVE
- CVE-2026-12010
- Published
- Jun 11, 2026
- Updated
- Jun 11, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 11, 2026CVE publishedPublication date reported by the CVE source.
- Jun 11, 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.115 <149.0.7827.115
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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