Heap corruption via WebGPU use-after-free
Published Jan 4, 2024 · Updated Jun 18, 2025
Use after free in WebGPU in Google Chrome before 120.0.6099.199 allows remote attackers to corrupt heap memory via crafted HTML. Google has not published the freed object, function, or invalid lifetime operation; the referenced Chromium bug requires permission. A victim must load the crafted page; public records establish heap corruption but do not document code execution or a sandbox escape.
Summary
What happened
Use after free in WebGPU in Google Chrome before 120.0.6099.199 allows remote attackers to corrupt heap memory via crafted HTML. Google has not published the freed object, function, or invalid lifetime operation; the referenced Chromium bug requires permission. A victim must load the crafted page; public records establish heap corruption but do not document code execution or a sandbox escape.
The record
- CVE
- CVE-2024-0225
- Published
- Jan 4, 2024
- Updated
- Jun 18, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 4, 2024CVE publishedPublication date reported by the CVE source.
- Jun 18, 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=120.0.6099.199 <120.0.6099.199
What conditions does exploitation require?
What is affected?
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