Heap corruption via unchecked Maglev input count
Published Sep 24, 2025 · Updated Sep 24, 2025
Integer overflow in V8 in Google Chrome before 140.0.7339.207 allows remote attackers to corrupt heap memory via crafted HTML. The Maglev graph builder adds parameter, argument-register, and fixed-input counts without first enforcing Node::kMaxInputs, then creates an oversized GeneratorStore node. A victim must load the page; successful exploitation can compromise browser data, integrity, and availability within the renderer sandbox.
Summary
What happened
Integer overflow in V8 in Google Chrome before 140.0.7339.207 allows remote attackers to corrupt heap memory via crafted HTML. The Maglev graph builder adds parameter, argument-register, and fixed-input counts without first enforcing Node::kMaxInputs, then creates an oversized GeneratorStore node. A victim must load the page; successful exploitation can compromise browser data, integrity, and availability within the renderer sandbox.
The record
- CVE
- CVE-2025-10892
- Published
- Sep 24, 2025
- Updated
- Sep 24, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-472, CWE-190, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 24, 2025CVE publishedPublication date reported by the CVE source.
- Sep 24, 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=140.0.7339.207 <140.0.7339.207
What conditions does exploitation require?
What is affected?
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