EUVD-2026-93754
GHSA-whj7-rphv-q9jq
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to crafted HTML page
-
DeliveryPage drives malicious WebGPU/Dawn operations
-
ExploitTrigger incomplete cleanup (CWE-459)
-
ExecutionCorrupt reused resource state
-
PersistEscape renderer sandbox
-
ImpactExecute arbitrary code on host
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Incomplete cleanup
|
| Exploitation Conditions | Exploitation requires the victim to use Chrome's Dawn/WebGPU graphics subsystem and to visit or render attacker-controlled HTML content (CVSS UI:R), so it is not fully drive-by silent - user interaction such as opening a malicious page is needed. The affected component is Dawn, Chrome's WebGPU implementation, so WebGPU must be reachable/enabled for the crafted content to trigger the incomplete-cleanup (CWE-459) condition. Limiting factors: the attack is probabilistic ('potentially execute arbitrary code'), it depends on the renderer reaching the vulnerable Dawn code path, and it is fixed in Chrome 155.0.8059.39 and later. No authentication is required (PR:N), but the required user interaction and the inherent difficulty of chaining a cleanup bug into a reliable sandbox escape meaningfully limit real-world exploitation. |
| Impact | Signals conflict and must be weighed carefully. The provided CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H = 9.6 Critical) reflects a remote, unauthenticated, scope-changing sandbox escape reachable from a web page, which is inherently serious. However, Google's own Chromium severity rating is only 'Medium', a notable divergence from the 9.6 Critical CVSS - this gap exists because Chromium severity weighs exploitability and real-world reliability of a Dawn/WebGPU incomplete-cleanup (CWE-459) bug, which typically requires precise heap/resource state and the word 'potentially' in the description signals non-deterministic code execution. No EPSS score, KEV listing, or POC was provided; therefore there is no public exploit identified at time of analysis and no evidence of active exploitation. Net assessment: patch promptly because it is a networked sandbox-escape primitive in ubiquitous software, but it is not a drop-everything emergency on the level of a KEV-listed, actively-exploited flaw. The CVSS-vs-Chromium-severity disagreement should be noted explicitly to stakeholders rather than citing 9.6 as settled truth. |
| Exploit ScenarioDerived | An attacker hosts or compromises a web page containing crafted WebGPU/Dawn content and lures a victim running a pre-155.0.8059.39 Chrome build to visit it. The incomplete-cleanup condition is triggered during rendering and leveraged to execute code outside the renderer sandbox on the victim's host. No public proof-of-concept was provided, and exploitation of memory-cleanup bugs for reliable sandbox escape is non-trivial. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 06, 2026
Incomplete cleanup in Dawn, Chrome's WebGPU implementation, allows a crafted HTML page to potentially corrupt GPU-process state and achieve code execution outside the browser sandbox in Google Chrome builds prior to 155.0.8059.39. Exploitation requires the victim to render attacker-controlled content that reaches the affected WebGPU/Dawn code path (CVSS UI:R with PR:N - unauthenticated remote attackers, but user interaction required), and the outcome is probabilistic rather than a guaranteed silent drive-by; the published base score is 9.6 while Google rates the issue Medium, and our assessed vector raises attack complexity to AC:H to reflect the difficulty of chaining a cleanup flaw into a reliable sandbox escape. No public exploit code has been identified at time of analysis, and Google has released Chrome 155.0.8059.39 as the fix.
RemediationAI
Upgrade to Google Chrome 155.0.8059.39 or later - the vendor-released patch - and allow the automatic updater to install it, confirming the build at chrome://version; release notes are at https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_086471744.html. Where immediate updating is not possible, the vulnerable Dawn code path can be made harder to reach by disabling WebGPU (via chrome://flags or the equivalent enterprise policy where configured), accepting the trade-off that GPU-accelerated and WebGPU-based web applications will break or degrade. Because exploitation requires the victim to render crafted HTML (CVSS UI:R), restricting browsing of untrusted pages and reinforcing user awareness of suspicious links also lowers exposure. No public exploit code is known, so prioritize the patch based on how much WebGPU-enabled browsing occurs in your environment rather than on emergency workarounds.
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
The flaw is an incomplete-cleanup defect (CWE-459) in Dawn, the cross-platform C++ WebGPU implementation bundled with Chromium and executed in Chrome's GPU process; because renderer and GPU processes sit behind Chrome's site-isolation sandbox, a cleanup bug that leaves stale objects, dangling handles, or un-released GPU resources can be reused by attacker-influenced WebGPU commands, which is why the impact is scoped as a sandbox escape (S:C) with high confidentiality, integrity, and availability impact. The affected package is the wildcard google:chrome CPE, and ENISA's EUVD entry lists the vulnerable range as Chrome builds below 155.0.8059.39. The CVSS vector (AV:N/PR:N/UI:R) confirms unauthenticated remote reach with mandatory user interaction, while our assessed vector uses AC:H rather than AC:L because the attacker must win a probabilistic state-reuse condition and reach WebGPU-enabled code paths, matching Google's own Medium Chromium severity rating.
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
Remote web-delivered with no auth (AV:N/PR:N) but victim must load the page (UI:R); AC:H because an incomplete-cleanup bug needs specific resource state for 'potential' code execution; sandbox escape gives S:C and full C/I/A:H.
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
Incomplete cleanup in Dawn in Google Chrome prior to 155.0.8059.39 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Medium)
Executive ViewAI
Google Chrome's WebGPU implementation, Dawn, contains a flaw that allows crafted web content to break out of the browser's sandbox and execute code with the logged-in user's privileges. Because Chrome runs on nearly every corporate workstation, successful exploitation would convert routine web browsing into an endpoint compromise path that defeats the browser isolation control security teams rely on. No public exploit code has been identified at time of analysis, and a vendor fix is already available, so the risk is containable through rapid, fleet-wide patching.
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
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Exploit-DB