Sandboxed code execution via uninitialized V8 resource
Published Sep 1, 2026 · Updated Sep 3, 2026
Uninitialized resource use in V8 in Google Chrome before 152.0.7977.75 allows remote attackers to execute code via crafted HTML. Google identifies V8 as the locus but has not published which resource remains uninitialized or how crafted HTML reaches the faulty operation. Opening attacker-controlled HTML is required, and successful exploitation is confined to arbitrary code execution inside the Chrome sandbox.
Summary
What happened
Uninitialized resource use in V8 in Google Chrome before 152.0.7977.75 allows remote attackers to execute code via crafted HTML. Google identifies V8 as the locus but has not published which resource remains uninitialized or how crafted HTML reaches the faulty operation. Opening attacker-controlled HTML is required, and successful exploitation is confined to arbitrary code execution inside the Chrome sandbox.
The record
- CVE
- CVE-2026-84326
- Published
- Sep 1, 2026
- Updated
- Sep 3, 2026
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 1, 2026CVE publishedPublication date reported by the CVE source.
- Sep 3, 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.75 <152.0.7977.75
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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.
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo