Sandbox escape via WebGL use after free
Published Jun 24, 2026 · Updated Jun 24, 2026
Use after free in WebGL in Google Chrome on Android before 149.0.7827.197 allows remote attackers to escape the sandbox via crafted HTML. The WebGL implementation continues to use an object after it has been freed, but Google has not disclosed the object, code path, or triggering input sequence. Exploitation requires a user to open the page, after which attacker-controlled code can cross the renderer sandbox boundary and affect the host process.
Summary
What happened
Use after free in WebGL in Google Chrome on Android before 149.0.7827.197 allows remote attackers to escape the sandbox via crafted HTML. The WebGL implementation continues to use an object after it has been freed, but Google has not disclosed the object, code path, or triggering input sequence. Exploitation requires a user to open the page, after which attacker-controlled code can cross the renderer sandbox boundary and affect the host process.
The record
- CVE
- CVE-2026-13032
- Published
- Jun 24, 2026
- Updated
- Jun 24, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 24, 2026CVE publishedPublication date reported by the CVE source.
- Jun 24, 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.197 <149.0.7827.197
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