Heap corruption via V8 use-after-free
Published Feb 4, 2025 · Updated Feb 7, 2025
Use-after-free in V8 in Google Chrome before 133.0.6943.53 allows remote attackers to trigger heap corruption via crafted HTML. Chrome identifies the locus only as V8; the restricted issue does not disclose which object is freed or which later operation dereferences it. A user must load attacker-controlled content, and the published record bounds the result to potential heap corruption rather than confirmed sandbox escape or code execution.
Summary
What happened
Use-after-free in V8 in Google Chrome before 133.0.6943.53 allows remote attackers to trigger heap corruption via crafted HTML. Chrome identifies the locus only as V8; the restricted issue does not disclose which object is freed or which later operation dereferences it. A user must load attacker-controlled content, and the published record bounds the result to potential heap corruption rather than confirmed sandbox escape or code execution.
The record
- CVE
- CVE-2025-0445
- Published
- Feb 4, 2025
- Updated
- Feb 7, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 4, 2025CVE publishedPublication date reported by the CVE source.
- Feb 7, 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=133.0.6943.53 <133.0.6943.53
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