Heap corruption via V8 type confusion
Published Mar 10, 2025 · Updated Feb 26, 2026
Type confusion in V8 in Google Chrome before 134.0.6998.88 allows remote attackers to corrupt heap memory via a crafted HTML page. Google has not disclosed the affected V8 code path or the incompatible-type operation because the referenced issue remains access-restricted. Reachability requires a user to load attacker-controlled HTML; the published record establishes heap corruption but does not specify the post-corruption outcome.
Summary
What happened
Type confusion in V8 in Google Chrome before 134.0.6998.88 allows remote attackers to corrupt heap memory via a crafted HTML page. Google has not disclosed the affected V8 code path or the incompatible-type operation because the referenced issue remains access-restricted. Reachability requires a user to load attacker-controlled HTML; the published record establishes heap corruption but does not specify the post-corruption outcome.
The record
- CVE
- CVE-2025-1920
- Published
- Mar 10, 2025
- Updated
- Feb 26, 2026
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-843, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 10, 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=134.0.6998.88 <134.0.6998.88
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