Heap corruption via undisclosed V8 implementation flaw
Published Nov 12, 2025 · Updated Nov 12, 2025
Heap corruption in V8 in Google Chrome before 142.0.7444.166 allows remote attackers to corrupt browser memory via crafted HTML. Google has not disclosed the affected V8 code path or the incorrect operation that permits the corruption. A user must load attacker-controlled HTML, and the public record establishes heap corruption but does not specify a resulting crash, code execution, or sandbox escape.
Summary
What happened
Heap corruption in V8 in Google Chrome before 142.0.7444.166 allows remote attackers to corrupt browser memory via crafted HTML. Google has not disclosed the affected V8 code path or the incorrect operation that permits the corruption. A user must load attacker-controlled HTML, and the public record establishes heap corruption but does not specify a resulting crash, code execution, or sandbox escape.
The record
- CVE
- CVE-2025-13042
- Published
- Nov 12, 2025
- Updated
- Nov 12, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 12, 2025CVE publishedPublication date reported by the CVE source.
- Nov 12, 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=142.0.7444.166 <142.0.7444.166
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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