EUVD-2026-50596
GHSA-jgwr-xg86-4cxr
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to crafted HTML page
-
DeliveryServe malicious WebGL/graphics content
-
ExploitTrigger input-validation flaw in ANGLE
-
ExecutionEscape renderer sandbox boundary
-
ImpactExecute code outside browser containment
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 actively load attacker-controlled web content in an unpatched Chrome build (before 151.0.7922.72) - the required user interaction (UI:R) is the primary limiting factor, as the attacker cannot trigger it without the user visiting the crafted HTML page. The specific technical prerequisite is that ANGLE processes the malicious graphics/WebGL input from that page; environments with hardware acceleration/WebGL disabled reduce exposure. Per the description ('potentially perform a sandbox escape') and Google's Medium severity rating, reliable exploitation likely also depends on chaining with a separate renderer-level vulnerability, meaning this is probably not independently exploitable to full escape on its own. No authentication is required (PR:N). |
| Impact | The signals conflict and should be weighed carefully. The assigned CVSS 3.1 base score is 9.6 (Critical), driven by network vector (AV:N), low complexity (AC:L), no privileges (PR:N), and a scope change (S:C) reflecting the sandbox-escape impact - but it does require user interaction (UI:R, i.e. visiting a page). Notably, Google's own Chromium severity rating is only 'Medium', and the description hedges with 'potentially perform a sandbox escape,' suggesting the flaw likely needs chaining with a separate renderer compromise rather than being independently weaponizable - a common reason NVD-style scores diverge sharply from vendor triage. Supporting the lower-urgency read: EPSS is just 0.18% (8th percentile), it is NOT on CISA KEV, and no POC is known. This is best treated as a standard 'patch on the normal Chrome auto-update cycle' item rather than an emergency, while recognizing sandbox-escape bugs are attractive for chaining. Conflict to note explicitly: CVSS 9.6 Critical vs. vendor 'Medium' and low EPSS - real-world risk is materially lower than the raw score implies. |
| Exploit ScenarioDerived | An attacker crafts a malicious HTML page containing specially formed WebGL/graphics content that triggers the ANGLE input-validation flaw, then lures a victim into visiting it via phishing, a malicious ad, or a compromised site. When the page loads in an unpatched Chrome, the crafted input drives ANGLE to potentially escape the renderer sandbox, allowing code to run outside the browser's containment - most plausibly as one link in a multi-stage exploit chain. No public exploit code is currently identified. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 31, 2026
Sandbox escape in Google Chrome's ANGLE graphics layer (versions prior to 151.0.7922.72) allows a remote attacker who lures a victim to a crafted HTML page to potentially break out of the renderer sandbox, undermining the browser's core containment boundary. The flaw stems from insufficient validation of untrusted input (CWE-20) in ANGLE, Chrome's WebGL/OpenGL-to-native translation layer. It was reported internally by the Chrome team; there is no public exploit identified at time of analysis, and the EPSS score is low at 0.18% (8th percentile).
RemediationAI
Vendor-released patch: update Google Chrome to 151.0.7922.72 or later on the desktop stable channel (Windows, macOS, Linux); Chrome typically applies this automatically, so ensure auto-update is enabled and restart the browser to complete installation, verifying via chrome://settings/help. Users of Chromium-based browsers should install the equivalent updated build from their respective vendors once available. Refer to the Chrome Releases advisory (https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.html) and the Chromium issue tracker (https://issues.chromium.org/issues/518243653). If patching must be delayed, compensating controls include restricting exposure to untrusted web content and, for managed fleets, disabling hardware-accelerated graphics/WebGL via enterprise policy (e.g., the HardwareAccelerationModeEnabled policy) to reduce ANGLE's attack surface - with the trade-off that this degrades graphics performance and can break WebGL-dependent sites and applications.
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 Chromium's abstraction library that translates OpenGL ES / WebGL API calls issued by web content into the platform's native graphics backend (Direct3D, Metal, Vulkan, or desktop GL). Because ANGLE processes attacker-influenced graphics commands from within the GPU/renderer process, a validation defect here is security-sensitive. The root cause is classified as CWE-20 (Improper Input Validation): untrusted data from a crafted page is not adequately checked before use in ANGLE, which - per the CVSS scope-change (S:C) metric - can let malicious content cross the process/sandbox boundary that normally isolates renderer code from the host. The single affected CPE is cpe:2.3:a:google:chrome (all versions below the fixed 151.0.7922.72 stable release).
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
Sources disagree (Medium–Critical)AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Network-delivered via crafted page (AV:N) but needs user visit (UI:R) and, per vendor 'Medium'/'potentially', likely chaining and specific conditions (AC:H); sandbox escape yields scope change with high host impact.
vuln.today treats the vendor’s rating as authoritative. A higher third-party CVSS (e.g. CISA-ADP) is shown for transparency but does not drive the headline severity.
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: Medium)
Executive ViewAI
Google Chrome contains a critical sandbox escape vulnerability (CVE-2026-17847, CVSS 9.6) that allows remote attackers to breach the browser's core containment model through malicious webpages, potentially leading to complete system compromise. This vulnerability affects all Chrome users organization-wide and could enable attackers to execute arbitrary code with elevated privileges if users visit attacker-controlled sites. Immediate patching to version 151.0.7922.72 or later is essential to restore the browser's fundamental security guarantees.
Apply vendor patch.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
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