Sandboxed code execution via V8 type confusion
Published May 28, 2024 · Updated Oct 21, 2025
Type confusion in V8 in Google Chrome before 125.0.6422.112 allows remote attackers to execute arbitrary code inside its sandbox via crafted HTML. Google identifies the V8 JavaScript engine as the affected locus but has not published the incompatible object types or faulty operation. A victim must open attacker-controlled HTML, and the resulting execution remains inside Chrome's sandbox unless paired with a separate escape.
Summary
What happened
Type confusion in V8 in Google Chrome before 125.0.6422.112 allows remote attackers to execute arbitrary code inside its sandbox via crafted HTML. Google identifies the V8 JavaScript engine as the affected locus but has not published the incompatible object types or faulty operation. A victim must open attacker-controlled HTML, and the resulting execution remains inside Chrome's sandbox unless paired with a separate escape.
The record
- CVE
- CVE-2024-5274
- Published
- May 28, 2024
- Updated
- Oct 21, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-843, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 28, 2024Exploitation reportedCISA Known Exploited Vulnerabilities entry
- May 28, 2024CVE publishedPublication date reported by the CVE source.
- Oct 21, 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=0 <125.0.6422.112
- Affected versionversion=125.0.6422.112 <125.0.6422.112
What conditions does exploitation require?
What is affected?
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
- Google reported in-the-wild exploitationreported exploitation
- CISA Known Exploited Vulnerabilities entryknown exploited catalog
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