Sandboxed code execution via Scheduling use-after-free
Published May 22, 2024 · Updated Mar 27, 2025
Use-after-free in Google Chrome's Scheduling component before 125.0.6422.76 allows remote attackers to execute code inside the sandbox. Google identifies Scheduling as using freed memory but has not published the affected function or object-lifetime sequence. A user must load a crafted HTML page; exploitation runs attacker-controlled code within the renderer sandbox, with no documented sandbox escape.
Summary
What happened
Use-after-free in Google Chrome's Scheduling component before 125.0.6422.76 allows remote attackers to execute code inside the sandbox. Google identifies Scheduling as using freed memory but has not published the affected function or object-lifetime sequence. A user must load a crafted HTML page; exploitation runs attacker-controlled code within the renderer sandbox, with no documented sandbox escape.
The record
- CVE
- CVE-2024-5157
- Published
- May 22, 2024
- Updated
- Mar 27, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 22, 2024CVE publishedPublication date reported by the CVE source.
- Mar 27, 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=0 <125.0.6422.76
- Affected versionversion=125.0.6422.76 <125.0.6422.76
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