Sandboxed code execution via V8 type confusion
Published May 15, 2024 · Updated Dec 16, 2025
Type confusion in V8 in Google Chrome before 125.0.6422.60 allows remote attackers to execute code inside the sandbox via a crafted HTML page. Public records identify the locus only as V8 and do not disclose which value receives an incompatible type or which operation misuses it. A user must load the crafted page; successful exploitation provides code execution within Chrome’s sandbox, and Google reported exploitation in the wild.
Summary
What happened
Type confusion in V8 in Google Chrome before 125.0.6422.60 allows remote attackers to execute code inside the sandbox via a crafted HTML page. Public records identify the locus only as V8 and do not disclose which value receives an incompatible type or which operation misuses it. A user must load the crafted page; successful exploitation provides code execution within Chrome’s sandbox, and Google reported exploitation in the wild.
The record
- CVE
- CVE-2024-4947
- Published
- May 15, 2024
- Updated
- Dec 16, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-843, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 15, 2024CVE publishedPublication date reported by the CVE source.
- Dec 16, 2025Record 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=125.0.6422.60 <125.0.6422.60
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.
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.
Reported exploitation
- CISA Known Exploited Vulnerabilities entryknown exploited catalog
- Google in-the-wild exploitation reportreported exploitation
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