EUVD-2026-90120
GHSA-78cg-f2wf-fp4f
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-priv local/guest session
-
DeliveryCraft malicious kernel escape call
-
ExploitBypass client-context authorization check
-
ExecutionExecute privileged kernel operation
-
ImpactEscalate to kernel / code execution
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization logic validation
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires local access to a system running the NVIDIA GPU Display Driver for Windows and a low-privileged authenticated session (PR:L); no user interaction is needed. The specific trigger is a kernel-mode escape (ioctl/escape) path where an authorization check meant to restrict operations by client execution context can be bypassed. Limiting factors: exploitation is strictly local (AV:L) - there is no remote/network attack surface - the attacker must already be able to run code on the host or, in vGPU/VDI deployments, control a guest driver instance under the Virtual GPU Manager; scope is unchanged (S:U), so impact is confined to the local system's kernel. Highest-value targets are multi-user, VDI, and cloud-GPU hosts where an untrusted tenant can reach the driver escape interface. |
| Impact | This is a genuine but access-gated privilege-escalation risk, not a remote-exploitable emergency. The CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H = 7.8, HIGH) is internally consistent with the description: the attacker needs LOCAL access and LOW privileges (an ordinary authenticated user session on a machine running the driver), no user interaction, and on success gains full C/I/A impact via an authorization-check bypass in kernel-mode escape handling. No EPSS score, no CISA KEV listing, and no public POC are present in the provided data, so there is no evidence of active or imminent widespread exploitation. The 'RCE' tag overstates reach - because AV:L, any code execution is local escalation to kernel context, not network-delivered RCE. Net: prioritize as a standard high-severity local kernel LPE for patch cycles, elevated in multi-tenant/shared-GPU contexts (the Guest Driver / Virtual GPU Manager tags imply vGPU/VDI/cloud-GPU exposure where a low-priv tenant escalating on the host is materially worse). No key signals conflict, but note the absence of EPSS/KEV/POC means exploitation likelihood is unquantified rather than confirmed-low. |
| Exploit ScenarioDerived | A low-privileged local user (or a guest VM tenant on a vGPU host) issues a crafted kernel-mode escape/ioctl to the NVIDIA display driver that is not properly restricted by the intended client-execution-context authorization check, causing the privileged operation to execute on their behalf. This yields escalation to kernel privileges, enabling code execution, data tampering, information disclosure, or a bug-check DoS. No public exploit code is identified at time of analysis, and local access plus a valid session are prerequisites. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 30, 2026
Privilege escalation in NVIDIA's GPU Display Driver for Windows lets a local, low-privileged authenticated user bypass an authorization check in the driver's kernel-mode escape handling, gaining kernel-level capabilities that can lead to code execution, data tampering, information disclosure, or denial of service on the affected host. The issue is classified as CWE-863 (incorrect authorization) with a CVSS 3.1 base score of 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H); it is strictly local with no remote or network attack surface. No public exploit code has been identified and the vulnerability is not listed on CISA KEV, so it should be treated as a genuine but access-gated privilege-escalation risk concentrated in multi-user, VDI, and cloud-GPU hosts where an untrusted tenant or guest driver instance can reach the driver's escape interface.
RemediationAI
The primary fix is to update the NVIDIA GPU Display Driver for Windows to the patched driver release identified in NVIDIA's product-security advisory for this issue (https://github.com/NVIDIA/product-security/tree/main/2026/5861), applying the corresponding branch update for each affected family - GeForce, RTX/Quadro/NVS, Tesla, and, where deployed, the Guest Driver and Virtual GPU Manager components in vGPU environments. Patch status per the vendor advisory should be considered available, but no exact fix version number is present in the provided data, so do not assume a specific version: obtain the current fixed release directly from NVIDIA's advisory or driver download page rather than from third-party mirrors. Where immediate patching is not possible, the exploit prerequisites (AV:L and PR:L) mean effective compensating controls are host-side access restrictions: limit interactive logon and code-execution rights on GPU-bearing hosts so that only trusted administrators can run arbitrary local processes, and restrict which local accounts or service contexts may open the NVIDIA kernel driver's device interface (for example by tightening the device object ACLs on the display/kernel driver handles) - the trade-off is that over-restricting device access will break GPU acceleration, CUDA/compute workloads, and remote-desktop or gaming sessions for the affected accounts. In VDI and multi-tenant cloud-GPU deployments, treat the guest driver and Virtual GPU Manager path as hostile: segregate or pin untrusted tenants to hosts that are fully patched first, avoid assigning untrusted guests to shared kernels with sensitive workloads, and be aware that disabling or withholding the guest driver removes GPU acceleration for those tenants entirely. There is no substitute for the vendor patch, and because the issue is local privilege escalation, no network-edge filtering or WAF-style mitigation is applicable.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 3 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The affected component is the NVIDIA GPU Display Driver for Windows, specifically its kernel-mode escape (ioctl) handling. The CPE data shows coverage across the consumer and professional/enterprise driver branches - NVIDIA GeForce, the RTX/Quadro/NVS line, and the Tesla/data-center line - as well as the Guest Driver and Virtual GPU Manager components used in vGPU and VDI deployments. The root-cause class is CWE-863, Incorrect Authorization: the driver performs an authorization check that is intended to restrict certain escape operations according to the calling client's execution context (for example, distinguishing a privileged host/admin caller from a less privileged client or a guest-driver instance routed through the Virtual GPU Manager), but that check can be bypassed so an operation is performed in a context it was never meant to reach. Because the vulnerable path is in kernel mode, a successful bypass escalates the caller from a low-privileged local user into kernel-privileged execution, with the CVSS impact metrics showing high confidentiality, integrity, and availability loss (C:H/I:H/A:H) while scope remains unchanged (S:U), meaning impact is confined to the local system and does not cross a security boundary into other components. Exploitation is gated by AV:L and PR:L - the attacker must already be able to execute code locally and hold at least a low-privileged authenticated session - and requires no user interaction (UI:N).
Know when Windows gets its next vulnerability
- 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:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Local low-priv user triggers a kernel authorization bypass with no interaction, yielding full local kernel compromise; scope unchanged, so C/I/A all High at AV:L/PR:L.
Primary rating from Vendor (nvidia).
CVSS VectorVendor: nvidia
DescriptionCVE.org
NVIDIA GPU Display Driver for Windows contains a vulnerability in kernel-mode escape handling where an attacker with local access could bypass an authorization check that is intended to restrict certain operations based on client execution context. A successful exploit of this vulnerability might lead to escalation of privilege, information disclosure, data tampering, denial of service, or code execution.
Articles & Coverage 3
Executive ViewAI
NVIDIA's GPU Display Driver for Windows carries a high-severity privilege-escalation flaw (CVE-2026-47571) that allows a low-privileged local user to reach kernel-level control of the host. The realistic exposure is concentrated in environments that share GPU hardware across users or tenants - VDI farms, remote-work platforms, and cloud-GPU instances - where a single hostile or compromised account could escalate to host-wide code execution, data tampering, or service disruption. Because no vendor patch is available yet, leadership should treat this as a containment and monitoring problem rather than a routine update item.
No vendor-released patch is identified at time of analysis. Interim mitigations: restrict local interactive and console logon rights on shared GPU hosts so untrusted users cannot access the driver's escape interface; enforce least privilege with sessions running as non-administrators; strengthen isolation between VDI sessions and tenants, and disable GPU passthrough to untrusted guests where not operationally required; deploy EDR with kernel-mode monitoring and alerting on anomalous driver escape or privilege transitions; and reduce the number of accounts with local access to multi-user GPU systems. Apply vendor patch when released.
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
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
Unauthenticated remote code execution in SmarterTools SmarterMail lets an attacker upload arbitrary files to any locatio
Windows Win32k fails to properly handle objects in memory, allowing local privilege escalation exploited in the wild in
A privilege escalation vulnerability (CVSS 5.5). Risk factors: actively exploited (KEV-listed), EPSS 94% exploitation pr
Windows Internet Shortcut Files (.url) contain an external control vulnerability (CVE-2025-33053, CVSS 8.8) that enables
Windows SMB contains an improper access control vulnerability (CVE-2025-33073, CVSS 8.8) enabling authenticated attacker
Twonky Server 8.5.2 on Linux and Windows allows unauthenticated access to the admin log file through a web service API b
An unrestricted file upload vulnerability exists in MiniWeb HTTP Server <= Build 300 that allows unauthenticated remote
FreeFloat FTP Server contains multiple critical design flaws that allow unauthenticated remote attackers to upload arbit
Serviio Media Server versions 1.4 through 1.8 on Windows contain an unauthenticated command injection in the /rest/actio
Twonky Server 8.5.2 uses hard-coded cryptographic keys for encrypting the administrator password. Combined with the cred
Mako Server versions 2.5 and 2.6 contain an unauthenticated OS command injection via the tutorial interface at examples/
React Native Metro Development Server binds to external interfaces by default and contains an OS command injection endpo
Exploit-DB