Heap corruption via incorrect veneer instruction count
Published Jul 15, 2025 · Updated Feb 26, 2026
Integer overflow in V8 in Google Chrome before 138.0.7204.157 allows remote attackers to corrupt heap memory through a crafted HTML page. ARM64 code-generation paths pass an incorrect instruction count to InstructionAccurateScope, letting veneer-distance accounting overflow after the scope ends. A user must open attacker-controlled HTML that drives V8's Maglev JIT; resulting heap corruption can crash the browser or enable code execution in its process.
Summary
What happened
Integer overflow in V8 in Google Chrome before 138.0.7204.157 allows remote attackers to corrupt heap memory through a crafted HTML page. ARM64 code-generation paths pass an incorrect instruction count to InstructionAccurateScope, letting veneer-distance accounting overflow after the scope ends. A user must open attacker-controlled HTML that drives V8's Maglev JIT; resulting heap corruption can crash the browser or enable code execution in its process.
The record
- CVE
- CVE-2025-7656
- Published
- Jul 15, 2025
- Updated
- Feb 26, 2026
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-472, T1189, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 15, 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=138.0.7204.157 <138.0.7204.157
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
- V8 Maglev 40,000-argument reproductionproof of concept · demonstrated
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