Sandbox escape via insufficient GPU policy enforcement
Published Jun 30, 2026 · Updated Jun 30, 2026
Insufficient GPU policy enforcement in Google Chrome before 150.0.7871.47 allows remote attackers to escape the renderer sandbox. Google identifies the GPU component as the locus, but the linked Chromium issue remains access-restricted and no public patch diff identifies the policy check or operation that fails. Exploitation requires an attacker-controlled renderer and a crafted HTML page; the published record establishes a sandbox escape but does not describe post-escape host actions.
Summary
What happened
Insufficient GPU policy enforcement in Google Chrome before 150.0.7871.47 allows remote attackers to escape the renderer sandbox. Google identifies the GPU component as the locus, but the linked Chromium issue remains access-restricted and no public patch diff identifies the policy check or operation that fails. Exploitation requires an attacker-controlled renderer and a crafted HTML page; the published record establishes a sandbox escape but does not describe post-escape host actions.
The record
- CVE
- CVE-2026-14037
- Published
- Jun 30, 2026
- Updated
- Jun 30, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-693, T1211
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 30, 2026CVE publishedPublication date reported by the CVE source.
- Jun 30, 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=150.0.7871.47 <150.0.7871.47
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