Sandbox escape via Core use-after-free
Published Sep 9, 2026 · Updated Sep 10, 2026
Use-after-free in Google Chrome Core before 153.0.8010.36 on Windows allows remote attackers to execute code outside the sandbox. The Core component accesses memory after freeing it while processing a crafted HTML page; Google has not disclosed the specific object or function involved. Exploitation requires an already compromised renderer process, and the resulting code execution crosses the renderer sandbox boundary.
Summary
What happened
Use-after-free in Google Chrome Core before 153.0.8010.36 on Windows allows remote attackers to execute code outside the sandbox. The Core component accesses memory after freeing it while processing a crafted HTML page; Google has not disclosed the specific object or function involved. Exploitation requires an already compromised renderer process, and the resulting code execution crosses the renderer sandbox boundary.
The record
- CVE
- CVE-2026-87524
- Published
- Sep 9, 2026
- Updated
- Sep 10, 2026
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, T1211
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 9, 2026CVE publishedPublication date reported by the CVE source.
- Sep 10, 2026Record 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=153.0.8010.36 <153.0.8010.36
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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