Heap corruption via V8 out-of-bounds write
Published May 27, 2025 · Updated Feb 26, 2026
Out-of-bounds write in V8 in Google Chrome before 137.0.7151.55 allows remote attackers to corrupt heap memory via crafted HTML. The public record identifies V8 as the locus but does not disclose the faulty operation or code path that writes beyond its intended memory boundary. A user must load attacker-controlled HTML; successful memory corruption affects the browser process, while public sources do not establish sandbox escape or code execution.
Summary
What happened
Out-of-bounds write in V8 in Google Chrome before 137.0.7151.55 allows remote attackers to corrupt heap memory via crafted HTML. The public record identifies V8 as the locus but does not disclose the faulty operation or code path that writes beyond its intended memory boundary. A user must load attacker-controlled HTML; successful memory corruption affects the browser process, while public sources do not establish sandbox escape or code execution.
The record
- CVE
- CVE-2025-5280
- Published
- May 27, 2025
- Updated
- Feb 26, 2026
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 27, 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.55 <137.0.7151.55
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.
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