Heap corruption via WebGPU use-after-free
Published Dec 16, 2025 · Updated Dec 16, 2025
Use-after-free in WebGPU in Google Chrome before 143.0.7499.147 allows remote attackers to corrupt heap memory via crafted HTML. Google has not disclosed the affected WebGPU object or the lifetime error that leaves freed memory reachable. Exploitation requires a user to load the crafted page; the published record establishes heap corruption but not code execution.
Summary
What happened
Use-after-free in WebGPU in Google Chrome before 143.0.7499.147 allows remote attackers to corrupt heap memory via crafted HTML. Google has not disclosed the affected WebGPU object or the lifetime error that leaves freed memory reachable. Exploitation requires a user to load the crafted page; the published record establishes heap corruption but not code execution.
The record
- CVE
- CVE-2025-14765
- Published
- Dec 16, 2025
- Updated
- Dec 16, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 16, 2025CVE publishedPublication date reported by the CVE source.
- Dec 16, 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=143.0.7499.147 <143.0.7499.147
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