EUVD-2026-50777
GHSA-26pv-hgm3-4wj5
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessHost crafted WebGPU page
-
DeliveryLure victim to open in Chrome Android
-
ExploitSend malformed input to Dawn
-
ExecutionCorrupt GPU-process state
-
PersistEscape renderer/GPU sandbox
-
ImpactExecute code beyond sandbox
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 content: the CVSS vector specifies UI:R (user interaction required), so the target must open or navigate to a crafted HTML page in Chrome on Android - it is not a zero-click or server-side condition. The affected surface is the WebGPU/Dawn subsystem, so the victim's Chrome must process the page's WebGPU content (WebGPU is enabled by default in recent Chrome). Limiting factors: it affects only Chrome on Android prior to 151.0.7922.72; success is described as only 'potentially' achieving sandbox escape, implying a non-trivial exploit chain; and no authentication or attacker privileges are needed (PR:N), but the required user interaction and the absence of a known working exploit meaningfully reduce practical risk. |
| Impact | Signals here diverge and should be weighed carefully. CVSS is 9.6 Critical (AV:N/AC:L/PR:N/UI:R/S:C, full C/I/A impact), reflecting a remotely reachable, unauthenticated, sandbox-crossing bug that only needs the victim to open a page. Counterbalancing this, EPSS is low (0.31%, 23rd percentile), SSVC scores Exploitation as 'none' and Automatable as 'no', and there is no KEV listing and no public exploit identified - so real-world exploitation risk today appears limited and non-mass-scalable, even though the potential technical impact is 'total.' Note that Chrome's own severity is Critical and the description only says an attacker can 'potentially' escape the sandbox, which typically requires a working chain; also flagged: the intelligence tag says 'Information Disclosure' while the description and CVSS (I:H/A:H) describe a full sandbox escape - treat the tag as unreliable and defer to the CVSS/description. Given Chrome's ubiquity, patch promptly, but this reads as a high-severity-yet-not-yet-exploited issue rather than an active emergency. |
| Exploit ScenarioDerived | An attacker hosts a malicious web page containing crafted WebGPU/Dawn content and lures an Android Chrome user to open it via phishing link, malvertising, or a compromised site. When the page loads, the malformed input triggers the input-validation flaw in the GPU process and, if chained successfully, escapes the sandbox to run with elevated privileges on the device. No public exploit is identified at time of analysis, and the 'potentially' wording plus SSVC 'exploitation: none' suggest a reliable exploit chain is not currently known to be circulating. |
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 for Android before 151.0.7922.72 stems from insufficient input validation in Dawn, Chromium's WebGPU implementation, and allows a remote attacker who lures a victim to a crafted HTML page to potentially break out of the renderer/GPU-process sandbox (CVSS 9.6, scope-changed). There is no public exploit identified at time of analysis and the flaw is not in CISA KEV; EPSS is low at 0.31% (23rd percentile), consistent with SSVC rating exploitation as 'none' despite a 'total' technical impact. Chrome rates the underlying Chromium bug as Critical.
RemediationAI
Vendor-released patch: update Google Chrome on Android to 151.0.7922.72 or later via the Google Play Store, which is the primary and recommended fix; this should apply automatically for most managed and consumer devices but should be verified in enterprise fleets. Reference the Chrome release note at https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.html and the NVD entry https://nvd.nist.gov/vuln/detail/CVE-2026-17651. If patching cannot be completed immediately, a targeted compensating control is to disable WebGPU (the Dawn attack surface) via the chrome://flags 'Unsafe WebGPU' / WebGPU flags or enterprise policy where available - trade-off: this breaks GPU-accelerated web apps and games that rely on WebGPU. As a broader stopgap, restrict browsing on unpatched Android devices to trusted sites, since exploitation requires the victim to load a crafted page.
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
Dawn is Chromium's cross-platform implementation of the WebGPU standard, providing web pages low-level access to GPU compute and rendering through the browser's GPU process. Because WebGPU exposes a large, complex attack surface that parses and acts on richly structured, attacker-controllable command data, a CWE-20 (Improper Input Validation) defect here means untrusted input from a web page is not adequately checked before use, which can corrupt GPU-process state. The scope-changed CVSS metric (S:C) and 'sandbox escape' framing indicate the impact crosses the renderer/GPU sandbox boundary into a more privileged context. The single affected CPE is cpe:2.3:a:google:chrome, with the described impact specific to the Android build prior to 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
Remote, unauthenticated page-load reaches Dawn (AV:N/PR:N/UI:R); sandbox escapes typically need chaining and specific state, so AC:H; escape crosses the sandbox boundary (S:C) with full C/I/A impact.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
Lifecycle Timeline
4DescriptionCVE.org
Insufficient validation of untrusted input in Dawn in Google Chrome on Android 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 for Android versions before 151.0.7922.72 contain a critical sandbox escape vulnerability that could fully compromise mobile devices; no public exploit identified at time of analysis. Organizations must immediately update Chrome for Android to eliminate exposure before exploitation methods emerge.
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