Sandbox escape via GPU race condition
Published Apr 23, 2026 · Updated Apr 23, 2026
Race condition in Google Chrome on Windows before 147.0.7727.117 allows remote attackers to escape the browser sandbox via a crafted video file. The restricted Chromium issue identifies the GPU component but does not disclose the shared resource, competing operations, or timing window that produces the race. Processing attacker-controlled video content requires user interaction; a successful escape crosses the browser sandbox boundary and exposes host data and execution context.
Summary
What happened
Race condition in Google Chrome on Windows before 147.0.7727.117 allows remote attackers to escape the browser sandbox via a crafted video file. The restricted Chromium issue identifies the GPU component but does not disclose the shared resource, competing operations, or timing window that produces the race. Processing attacker-controlled video content requires user interaction; a successful escape crosses the browser sandbox boundary and exposes host data and execution context.
The record
- CVE
- CVE-2026-6921
- Published
- Apr 23, 2026
- Updated
- Apr 23, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-362, T1068
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 23, 2026CVE publishedPublication date reported by the CVE source.
- Apr 23, 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=147.0.7727.117 <147.0.7727.117
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