Sandbox escape via Views use-after-free
Published Jun 4, 2026 · Updated Jun 4, 2026
Use after free in Google Chrome's Views component before 149.0.7827.53 allows remote attackers to escape the renderer sandbox through crafted HTML. Public Google records do not disclose the affected Views object or the lifetime operation that leaves freed memory accessible. Exploitation requires an already-compromised renderer process, and the published consequence is crossing the renderer sandbox boundary.
Summary
What happened
Use after free in Google Chrome's Views component before 149.0.7827.53 allows remote attackers to escape the renderer sandbox through crafted HTML. Public Google records do not disclose the affected Views object or the lifetime operation that leaves freed memory accessible. Exploitation requires an already-compromised renderer process, and the published consequence is crossing the renderer sandbox boundary.
The record
- CVE
- CVE-2026-10988
- Published
- Jun 4, 2026
- Updated
- Jun 4, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-416, 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.
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