EUVD-2026-50781
GHSA-p3qq-x22v-cv22
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to crafted HTML page
-
DeliveryDeliver malicious WebGL/graphics content
-
ExploitTrigger input-validation flaw in ANGLE
-
ExecutionCorrupt GPU-process state
-
PersistEscape renderer sandbox
-
ImpactGain elevated access on host
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V2 - Validation and Business Logic Input validation, allowlisting
|
| Exploitation Conditions | Exploitation requires the victim to load attacker-controlled content in a vulnerable Chrome build (before 151.0.7922.72) that reaches ANGLE's graphics-input processing path - i.e., WebGL/WebGPU/graphics rendering must be active, which is the default when hardware acceleration is enabled. Per CVSS PR:N the attacker needs no authentication, but UI:R means user interaction is mandatory: the target must open or navigate to the crafted HTML page. Limiting factors are that the description says the escape is only 'potentially' achievable, strongly implying it must be chained with a separate renderer-compromise bug to be fully weaponized, and that disabling GPU acceleration removes the vulnerable code path. It affects Chrome desktop across platforms per the CPE. |
| Impact | The signals are mixed but lean toward priority patching. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H, score 9.6) indicates network-reachable, low-complexity, unauthenticated exploitation that only requires the victim to view a page, with a scope change reflecting the sandbox escape - a serious profile. Countering this, EPSS is only 0.31% (23rd percentile), the CVE is NOT in CISA KEV, and no public exploit has been identified, so there is no evidence of active or imminent widespread exploitation yet. Note also the description hedges with 'potentially perform a sandbox escape,' implying reliable exploitation likely requires chaining with a separate renderer bug - real-world exploitation is harder than the raw 9.6 suggests. The Tags field lists 'Information Disclosure,' which is narrower than the C:H/I:H/A:H full-impact CVSS vector; treat the CVSS impact as the authoritative signal for a sandbox escape. Given Chrome's ubiquity and Google's Critical rating, this warrants routine-but-prompt patching rather than emergency response. |
| Exploit ScenarioDerived | An attacker hosts a malicious web page containing crafted WebGL/graphics content and lures a victim (via phishing link, malvertising, or a compromised site) to open it in a vulnerable Chrome build. When ANGLE processes the untrusted graphics input, the validation flaw is triggered inside the GPU process, and - likely combined with a companion renderer exploit - the attacker escapes the sandbox to gain elevated access on the host. No public exploit has been identified at time of analysis, and the low AC plus network vector make delivery trivial, but the required user interaction (visiting the page) is the main gate. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 30, 2026
Sandbox escape in Google Chrome's ANGLE graphics layer, fixed in stable release 151.0.7922.72, lets a remote attacker who lures a victim to a crafted HTML page break out of the renderer sandbox and gain broader access on the host. Rated Critical by Chromium and scored CVSS 9.6, the flaw stems from insufficient validation of untrusted input (CWE-20) processed by ANGLE and carries a scope-changing impact. There is no public exploit identified at time of analysis and EPSS is low at 0.31% (23rd percentile), but the Critical rating and sandbox-escape primitive make prompt patching important.
RemediationAI
Vendor-released patch: 151.0.7922.72 - update Google Chrome to 151.0.7922.72 or later on all desktop platforms; Chrome typically auto-updates, so verify via chrome://settings/help and relaunch to apply, and confirm managed/enterprise fleets are not pinned to an older channel. Users of other Chromium-based browsers should apply the vendor build that incorporates the equivalent Chromium fix once available. No standalone workaround is provided by the vendor, but as an interim compensating control you can reduce GPU-process attack surface by disabling hardware acceleration (chrome://settings, 'Use graphics acceleration when available' off) or launching with --disable-gpu, which forces software rendering and largely removes the ANGLE code path - the trade-off is degraded WebGL/WebGPU performance, higher CPU use, and possible rendering glitches, so this is only a stopgap until the update is deployed. Reference the advisory at https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.html.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
ANGLE (Almost Native Graphics Layer Engine) is Chrome's graphics abstraction layer that translates OpenGL ES / WebGL / WebGPU calls from web content into the platform's native graphics API (Direct3D, Vulkan, or Metal). Because ANGLE runs inside Chrome's GPU process and parses complex, attacker-influenceable graphics command streams, a validation gap there is a high-value target. The root cause is classified as CWE-20 (Improper Input Validation): untrusted input from a web page is not sufficiently checked before ANGLE acts on it, and the resulting memory-safety or state-confusion condition can be leveraged to cross the renderer/GPU sandbox boundary. The affected component is identified in CPE as cpe:2.3:a:google:chrome, all versions prior to the fixed build 151.0.7922.72.
Know when the next one hits your stack
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Network-delivered crafted page needs no auth (PR:N) but requires the victim to visit it (UI:R); ANGLE lives in the sandboxed GPU process so a successful escape is scope-changing (S:C) with full host impact.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
Lifecycle Timeline
4DescriptionCVE.org
Insufficient validation of untrusted input in ANGLE in Google Chrome prior to 151.0.7922.72 allowed a remote attacker to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Critical)
Executive ViewAI
Google Chrome versions prior to 151.0.7922.72 contain a critical sandbox escape vulnerability in the ANGLE graphics layer that allows remote attackers to break out of the renderer process via a crafted HTML page, potentially gaining unauthorized access to the host system. No public exploit identified at time of analysis, but the Critical severity rating and sandbox-escape primitive create significant organizational risk requiring immediate remediation. All Chrome users across your organization are potentially affected.
Apply vendor patch.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
VulDB
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Related Vulnerabilities in Google Chrome Prior to 151.0.7922.72 Security Flaws
View all 80Same weakness CWE-20 – Improper Input Validation
View allSame technique Information Disclosure
View allVendor StatusVendor
SUSE
Severity: Critical| Product | Status |
|---|---|
| SUSE Package Hub 15 SP7 | Fixed |
| openSUSE Leap 16.0 | Fixed |
| SUSE Package Hub 15 SP7 | Affected |
Exploit-DB