Sandboxed code execution via WebGL use-after-free
Published Apr 1, 2026 · Updated Apr 1, 2026
Use after free in Google Chrome WebGL before 146.0.7680.178 allows remote attackers to execute code in the sandbox via crafted HTML. Google identifies dangling-object access in WebGL, but the restricted issue does not disclose the object, function, or lifetime error that leaves freed memory reachable. A user must load the attacker-controlled page; successful exploitation remains inside the renderer sandbox, with no sandbox escape established for this CVE.
Summary
What happened
Use after free in Google Chrome WebGL before 146.0.7680.178 allows remote attackers to execute code in the sandbox via crafted HTML. Google identifies dangling-object access in WebGL, but the restricted issue does not disclose the object, function, or lifetime error that leaves freed memory reachable. A user must load the attacker-controlled page; successful exploitation remains inside the renderer sandbox, with no sandbox escape established for this CVE.
The record
- CVE
- CVE-2026-5285
- Published
- Apr 1, 2026
- Updated
- Apr 1, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 1, 2026CVE publishedPublication date reported by the CVE source.
- Apr 1, 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=146.0.7680.178 <146.0.7680.178
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