Sandboxed code execution via Blink use-after-free
Published Aug 11, 2026 · Updated Aug 11, 2026
Use after free in Blink in Google Chrome before 151.0.7922.137 allows remote attackers to execute code in the sandbox via crafted HTML. Google identifies a freed-object lifetime error in Blink, but the restricted bug report leaves the affected Blink object and stale-reference path undisclosed. A user must open attacker-controlled HTML; resulting code execution remains inside Chrome's renderer sandbox, with no published sandbox escape for this CVE.
Summary
What happened
Use after free in Blink in Google Chrome before 151.0.7922.137 allows remote attackers to execute code in the sandbox via crafted HTML. Google identifies a freed-object lifetime error in Blink, but the restricted bug report leaves the affected Blink object and stale-reference path undisclosed. A user must open attacker-controlled HTML; resulting code execution remains inside Chrome's renderer sandbox, with no published sandbox escape for this CVE.
The record
- CVE
- CVE-2026-19560
- Published
- Aug 11, 2026
- Updated
- Aug 11, 2026
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 11, 2026CVE publishedPublication date reported by the CVE source.
- Aug 11, 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=151.0.7922.137 <151.0.7922.137
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