Heap corruption via V8 type confusion
Published Nov 17, 2025 · Updated Feb 26, 2026
Type confusion in V8 in Google Chrome before 142.0.7444.59 allows remote attackers to corrupt heap memory via a crafted HTML page. Google identifies the locus as V8 but has not published which operation confuses object types; the linked issue remains restricted. Exploitation requires a user to load attacker-controlled HTML and can compromise confidentiality, integrity, and availability within Chrome's security scope.
Summary
What happened
Type confusion in V8 in Google Chrome before 142.0.7444.59 allows remote attackers to corrupt heap memory via a crafted HTML page. Google identifies the locus as V8 but has not published which operation confuses object types; the linked issue remains restricted. Exploitation requires a user to load attacker-controlled HTML and can compromise confidentiality, integrity, and availability within Chrome's security scope.
The record
- CVE
- CVE-2025-13226
- Published
- Nov 17, 2025
- Updated
- Feb 26, 2026
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-843, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 17, 2025CVE publishedPublication date reported by the CVE source.
- Feb 26, 2026Record 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.59 <142.0.7444.59
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