Sandboxed code execution via V8 out-of-bounds write
Published Sep 29, 2026 · Updated Sep 29, 2026
Out-of-bounds write in V8 in Google Chrome before 154.0.8037.57 allows remote attackers to run code in the sandbox via crafted HTML. V8 writes beyond a memory boundary while processing attacker-controlled page content; Google has not disclosed the specific faulty routine or trigger. A victim must open the crafted page, and the reported execution remains inside Chrome's sandbox, with no documented sandbox escape.
Summary
What happened
Out-of-bounds write in V8 in Google Chrome before 154.0.8037.57 allows remote attackers to run code in the sandbox via crafted HTML. V8 writes beyond a memory boundary while processing attacker-controlled page content; Google has not disclosed the specific faulty routine or trigger. A victim must open the crafted page, and the reported execution remains inside Chrome's sandbox, with no documented sandbox escape.
The record
- CVE
- CVE-2026-95304
- Published
- Sep 29, 2026
- Updated
- Sep 29, 2026
- Vendor
- WebM Project
- Product
- Google Chrome
- Classifications
- T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 29, 2026CVE publishedPublication date reported by the CVE source.
- Sep 29, 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=154.0.8037.57 <154.0.8037.57
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.
Activity data is delayed. The latest report is Sep 28, 2026.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started