Heap corruption via V8 type confusion
Published Dec 14, 2023 · Updated Nov 4, 2025
Type confusion in V8 in Google Chrome before 120.0.6099.109 allows remote attackers to corrupt heap memory via crafted HTML. Google has not published the faulty V8 operation or disclosed how the engine assigns an incompatible type to attacker-controlled data. Exploitation requires a user to open crafted HTML; successful heap corruption compromises browser confidentiality, integrity, and availability.
Summary
What happened
Type confusion in V8 in Google Chrome before 120.0.6099.109 allows remote attackers to corrupt heap memory via crafted HTML. Google has not published the faulty V8 operation or disclosed how the engine assigns an incompatible type to attacker-controlled data. Exploitation requires a user to open crafted HTML; successful heap corruption compromises browser confidentiality, integrity, and availability.
The record
- CVE
- CVE-2023-6702
- Published
- Dec 14, 2023
- Updated
- Nov 4, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-843, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 14, 2023CVE publishedPublication date reported by the CVE source.
- Nov 4, 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=120.0.6099.109 <120.0.6099.109
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