Heap corruption via V8 type confusion
Published Oct 5, 2023 · Updated May 1, 2025
Type confusion in V8 in Google Chrome before 117.0.5938.149 allows remote attackers to corrupt heap memory via crafted HTML. The public advisory identifies V8 but keeps the bug record restricted, leaving the affected code path and incompatible types undisclosed. A user must load attacker-controlled content, after which heap corruption compromises the browser process's data, integrity, and availability.
Summary
What happened
Type confusion in V8 in Google Chrome before 117.0.5938.149 allows remote attackers to corrupt heap memory via crafted HTML. The public advisory identifies V8 but keeps the bug record restricted, leaving the affected code path and incompatible types undisclosed. A user must load attacker-controlled content, after which heap corruption compromises the browser process's data, integrity, and availability.
The record
- CVE
- CVE-2023-5346
- Published
- Oct 5, 2023
- Updated
- May 1, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-843, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 5, 2023CVE publishedPublication date reported by the CVE source.
- May 1, 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=117.0.5938.149 <117.0.5938.149
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