Sandboxed code execution via V8 out-of-bounds write
Published May 28, 2026 · Updated May 28, 2026
Out-of-bounds write in V8 in Google Chrome before 148.0.7778.216 allows remote attackers to run code inside its sandbox via crafted HTML. Google has not disclosed the V8 function, object, or input transformation responsible for the write beyond intended bounds. Exploitation requires a user to open an attacker-controlled page; the reported code execution remains inside Chrome's sandbox without a separate escape.
Summary
What happened
Out-of-bounds write in V8 in Google Chrome before 148.0.7778.216 allows remote attackers to run code inside its sandbox via crafted HTML. Google has not disclosed the V8 function, object, or input transformation responsible for the write beyond intended bounds. Exploitation requires a user to open an attacker-controlled page; the reported code execution remains inside Chrome's sandbox without a separate escape.
The record
- CVE
- CVE-2026-9973
- Published
- May 28, 2026
- Updated
- May 28, 2026
- Vendor
- WebM Project
- Product
- Chrome
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 28, 2026CVE publishedPublication date reported by the CVE source.
- May 28, 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 version<148.0.7778.216
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.
Activity data is delayed. The latest report is Sep 28, 2026.
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.
Contact us