EUVD-2026-50616
GHSA-58ff-pxwr-4jq2
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to crafted page
-
DeliveryDeliver malicious WebGPU/Dawn payload
-
ExploitTrigger improper input validation in Dawn
-
ExecutionAttempt renderer sandbox escape
-
ImpactAccess host beyond renderer boundary
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 Chrome's WebGPU path - i.e., a crafted HTML page that exercises the Dawn component, so the WebGPU feature must be reachable/enabled (default in modern Chrome). Per CVSS PR:N the attacker needs no authentication, but UI:R means user interaction is mandatory: the victim must navigate to or open the malicious page, which is the primary limiting factor. Exploitation is further limited by affecting only Chrome versions before 151.0.7922.72, by the Medium Chromium severity and hedged 'potentially' language suggesting a reliable sandbox escape may require chaining with another flaw, and by the low Low/Low/Low impact profile. |
| Impact | The signals are consistent but point to a moderate, not urgent, priority. The CVSS vector (AV:N/AC:L/PR:N/UI:R) shows a network-reachable, low-complexity, unauthenticated bug that nonetheless requires user interaction - the victim must open a malicious page - and the impacts are only Low across confidentiality, integrity, and availability despite the scope change, hence the 7.1 rather than a critical score. EPSS is very low (0.18%, 8th percentile), the vulnerability is NOT on CISA KEV, and no POC is referenced, so real-world exploitation pressure is currently low. The description hedges with 'potentially perform a sandbox escape,' indicating exploitation is not proven trivial; sandbox escapes in WebGPU typically require chaining with a renderer bug to be fully weaponized. Net: patch on the normal Chrome auto-update cadence rather than treating it as an emergency, but do not defer indefinitely given browsers are a prime target. |
| Exploit ScenarioDerived | An attacker hosts a malicious web page containing crafted WebGPU/Dawn calls and entices a victim to open it (via phishing link, malvertising, or a compromised site). When the page loads in an unpatched Chrome, the malformed input is processed by Dawn without adequate validation, potentially allowing the attacker to escape the renderer sandbox toward the host; no public POC is currently identified, and full compromise would likely require chaining with an additional renderer bug. |
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 Dawn (WebGPU) component affects all desktop Chrome builds prior to 151.0.7922.72, where insufficient validation of untrusted input lets a remote attacker who lures a victim to a crafted HTML page potentially break out of the renderer sandbox. Chromium rates the severity Medium and the issue carries a CVSS 7.1 with scope change, but there is no public exploit identified at time of analysis and EPSS is very low at 0.18% (8th percentile). Google has shipped a patched Stable channel release addressing it.
RemediationAI
Vendor-released patch: update Google Chrome to 151.0.7922.72 or later on all desktop platforms; Chrome's automatic updater will normally apply this, so verify via chrome://settings/help and relaunch to complete installation, and in managed fleets push the update through your management channel and confirm rollout. Reference the Chrome Releases advisory at https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.html. If immediate patching is not possible, the exploitation prerequisite of WebGPU means a compensating control is to disable WebGPU/Dawn by launching Chrome with --disable-features=WebGPU or via the corresponding enterprise policy, which blocks the affected code path at the cost of breaking legitimate WebGPU-based sites and applications; user-awareness measures to avoid untrusted links reduce but do not eliminate exposure since only a page visit is required.
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 open-source implementation of the WebGPU API, providing web pages low-level access to the GPU for compute and rendering. Because WebGPU exposes a large, complex native surface (command validation, resource binding, shader inputs) to untrusted JavaScript running in the sandboxed renderer, flaws here are a recurring sandbox-escape vector. The root cause is classified as CWE-20 (Improper Input Validation): Dawn does not sufficiently validate untrusted parameters supplied by web content, which can be leveraged to cross the renderer/host trust boundary - reflected in the CVSS scope change (S:C). The affected component matches CPE cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*.
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:L/I:L/A:L
Remote via crafted page (AV:N, PR:N) needing victim navigation (UI:R); AC:H because a reliable Dawn sandbox escape realistically requires winning conditions/chaining, with scope change (S:C) and Low CIA 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 Dawn 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 desktop environments face a critical vulnerability (CVE-2026-17867) that could enable attackers to break out of the browser sandbox and gain system-level access when users visit malicious web content. With Chrome deployed widely across the organization for business applications and external web access, this vulnerability directly threatens endpoint security and data confidentiality. Although exploitation probability currently remains very low per industry metrics, the severity of potential compromise warrants immediate patching across all Chrome instances.
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