Heap corruption via crafted HTML page
Published Jun 11, 2024 · Updated Feb 13, 2025
Inappropriate memory allocation in Google Chrome before 126.0.6478.54 allows remote attackers to trigger heap corruption via crafted HTML. Google identifies the Memory Allocator as the affected locus but has not disclosed the inconsistent operation that mishandles page-controlled input. A user must load the crafted page; the public record establishes heap corruption but does not establish code execution or a specific confidentiality impact.
Summary
What happened
Inappropriate memory allocation in Google Chrome before 126.0.6478.54 allows remote attackers to trigger heap corruption via crafted HTML. Google identifies the Memory Allocator as the affected locus but has not disclosed the inconsistent operation that mishandles page-controlled input. A user must load the crafted page; the public record establishes heap corruption but does not establish code execution or a specific confidentiality impact.
The record
- CVE
- CVE-2024-5839
- Published
- Jun 11, 2024
- Updated
- Feb 13, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-474, T1203, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 11, 2024CVE publishedPublication date reported by the CVE source.
- Feb 13, 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 <126.0.6478.54
- Affected versionversion=126.0.6478.54 <126.0.6478.54
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.
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