Heap corruption via V8 type confusion
Published Jan 16, 2024 · Updated Dec 16, 2025
Type confusion in V8 in Google Chrome before 120.0.6099.224 allows remote attackers to corrupt heap memory via crafted HTML. Google has not disclosed the affected V8 function or the incompatible-type operation that produces the corruption. A user must load the page; successful exploitation corrupts browser-process memory, while the published record does not specify resulting control or data access.
Summary
What happened
Type confusion in V8 in Google Chrome before 120.0.6099.224 allows remote attackers to corrupt heap memory via crafted HTML. Google has not disclosed the affected V8 function or the incompatible-type operation that produces the corruption. A user must load the page; successful exploitation corrupts browser-process memory, while the published record does not specify resulting control or data access.
The record
- CVE
- CVE-2024-0518
- Published
- Jan 16, 2024
- Updated
- Dec 16, 2025
- Vendor
- Fedora Project
- Product
- Fedora Linux
- Classifications
- CWE-843
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 16, 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=39
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.
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