Sandboxed code execution via V8 use-after-free
Published Jun 8, 2026 · Updated Jun 8, 2026
Use-after-free in V8 in Google Chrome before 149.0.7827.103 allows remote attackers to execute code in the sandbox via crafted HTML. Chrome identifies the locus only as V8; restricted bug details do not disclose which object is accessed after its lifetime ends. A user must load the attacker's HTML page, and successful exploitation runs code within Chrome's renderer sandbox rather than escaping it.
Summary
What happened
Use-after-free in V8 in Google Chrome before 149.0.7827.103 allows remote attackers to execute code in the sandbox via crafted HTML. Chrome identifies the locus only as V8; restricted bug details do not disclose which object is accessed after its lifetime ends. A user must load the attacker's HTML page, and successful exploitation runs code within Chrome's renderer sandbox rather than escaping it.
The record
- CVE
- CVE-2026-11649
- Published
- Jun 8, 2026
- Updated
- Jun 8, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 8, 2026CVE publishedPublication date reported by the CVE source.
- Jun 8, 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.103 <149.0.7827.103
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