Heap corruption via Maglev slice type confusion
Published Dec 2, 2025 · Updated Feb 26, 2026
Type confusion in V8 in Google Chrome before 143.0.7499.41 allows remote attackers to trigger heap corruption through crafted HTML. Maglev's Array.prototype.slice reducer applies a receiver-map optimization in a polymorphic branch whose receiver is known not to be a JSReceiver, creating incompatible type assumptions. Exploitation requires a user to load attacker-controlled HTML; successful corruption can expose or alter browser-process data or crash the browser.
Summary
What happened
Type confusion in V8 in Google Chrome before 143.0.7499.41 allows remote attackers to trigger heap corruption through crafted HTML. Maglev's Array.prototype.slice reducer applies a receiver-map optimization in a polymorphic branch whose receiver is known not to be a JSReceiver, creating incompatible type assumptions. Exploitation requires a user to load attacker-controlled HTML; successful corruption can expose or alter browser-process data or crash the browser.
The record
- CVE
- CVE-2025-13630
- Published
- Dec 2, 2025
- Updated
- Feb 26, 2026
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-843, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 2, 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=143.0.7499.41 <143.0.7499.41
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