Out-of-bounds memory access via V8 integer overflow
Published Jun 18, 2025 · Updated Feb 26, 2026
Integer overflow in V8 in Google Chrome before 137.0.7151.119 allows remote attackers to access memory out of bounds via crafted HTML. Google identifies V8 as the affected component but keeps the issue details restricted, so the overflowing operation and affected data path are undisclosed. Opening attacker-controlled HTML is required; the published record establishes out-of-bounds memory access but does not claim code execution.
Summary
What happened
Integer overflow in V8 in Google Chrome before 137.0.7151.119 allows remote attackers to access memory out of bounds via crafted HTML. Google identifies V8 as the affected component but keeps the issue details restricted, so the overflowing operation and affected data path are undisclosed. Opening attacker-controlled HTML is required; the published record establishes out-of-bounds memory access but does not claim code execution.
The record
- CVE
- CVE-2025-6191
- Published
- Jun 18, 2025
- Updated
- Feb 26, 2026
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-472, CWE-190, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 18, 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=137.0.7151.119 <137.0.7151.119
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