Heap corruption via Canvas use-after-free
Published Jan 30, 2024 · Updated May 29, 2025
Use after free in Canvas in Google Chrome before 121.0.6167.139 allows remote attackers to trigger heap corruption via crafted HTML. Google identifies the Canvas component as the locus but has not published which object is freed prematurely or which later Canvas operation dereferences it. A victim must load attacker-controlled HTML; successful exploitation can corrupt browser heap state, while the public record does not establish code execution or sandbox escape.
Summary
What happened
Use after free in Canvas in Google Chrome before 121.0.6167.139 allows remote attackers to trigger heap corruption via crafted HTML. Google identifies the Canvas component as the locus but has not published which object is freed prematurely or which later Canvas operation dereferences it. A victim must load attacker-controlled HTML; successful exploitation can corrupt browser heap state, while the public record does not establish code execution or sandbox escape.
The record
- CVE
- CVE-2024-1060
- Published
- Jan 30, 2024
- Updated
- May 29, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 30, 2024CVE publishedPublication date reported by the CVE source.
- May 29, 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=121.0.6167.139 <121.0.6167.139
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.
Weakness, pattern, technique
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