Sandboxed code execution via V8 use-after-free
Published Aug 25, 2026 · Updated Aug 25, 2026
Use-after-free in V8 in Google Chrome before 152.0.7977.65 allows remote attackers to execute arbitrary code via crafted HTML. Google identifies V8 as the affected component but has not disclosed the object, function, or code path that retains and later dereferences freed memory. A user must load the attacker-controlled page; resulting code execution remains inside Chrome's renderer sandbox, with no disclosed sandbox escape.
Summary
What happened
Use-after-free in V8 in Google Chrome before 152.0.7977.65 allows remote attackers to execute arbitrary code via crafted HTML. Google identifies V8 as the affected component but has not disclosed the object, function, or code path that retains and later dereferences freed memory. A user must load the attacker-controlled page; resulting code execution remains inside Chrome's renderer sandbox, with no disclosed sandbox escape.
The record
- CVE
- CVE-2026-78899
- Published
- Aug 25, 2026
- Updated
- Aug 25, 2026
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 25, 2026CVE publishedPublication date reported by the CVE source.
- Aug 25, 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=152.0.7977.65 <152.0.7977.65
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