Heap corruption via libvpx use-after-free
Published May 27, 2025 · Updated Nov 3, 2025
Use-after-free in libvpx in Google Chrome before 137.0.7151.55 allows remote attackers to trigger heap corruption through crafted HTML. Google identifies libvpx as the affected component but keeps the issue details restricted, leaving the freed object's lifetime error undisclosed. A user must load attacker-controlled HTML; the public record does not establish code execution, a browser escape, or service interruption.
Summary
What happened
Use-after-free in libvpx in Google Chrome before 137.0.7151.55 allows remote attackers to trigger heap corruption through crafted HTML. Google identifies libvpx as the affected component but keeps the issue details restricted, leaving the freed object's lifetime error undisclosed. A user must load attacker-controlled HTML; the public record does not establish code execution, a browser escape, or service interruption.
The record
- CVE
- CVE-2025-5283
- Published
- May 27, 2025
- Updated
- Nov 3, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 27, 2025CVE publishedPublication date reported by the CVE source.
- Nov 3, 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=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