Sandboxed code execution via V8 use-after-free
Published Sep 15, 2026 · Updated Sep 15, 2026
Use-after-free in V8 in Google Chrome before 153.0.8010.47 allows remote attackers to execute code inside the sandbox via crafted HTML. Google identifies V8 as the affected locus but has not disclosed the object lifetime error or triggering operation; the linked Chromium bug requires sign-in. A user must load the crafted page, and the reported execution remains inside the browser sandbox rather than demonstrating a sandbox escape.
Summary
What happened
Use-after-free in V8 in Google Chrome before 153.0.8010.47 allows remote attackers to execute code inside the sandbox via crafted HTML. Google identifies V8 as the affected locus but has not disclosed the object lifetime error or triggering operation; the linked Chromium bug requires sign-in. A user must load the crafted page, and the reported execution remains inside the browser sandbox rather than demonstrating a sandbox escape.
The record
- CVE
- CVE-2026-91745
- Published
- Sep 15, 2026
- Updated
- Sep 15, 2026
- Vendor
- The fscrypt Project
- Product
- Chrome
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 15, 2026CVE publishedPublication date reported by the CVE source.
- Sep 15, 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<153.0.8010.47
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