Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain low-privileged local access to vGPU host or guest VM
-
DeliveryCraft malformed vGPU Manager request or IOCTL
-
ExploitTrigger out-of-bounds write in host-side manager process
-
ExecutionCorrupt adjacent memory structures
-
ImpactCause denial of service, data tampering, or information disclosure
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, write limits
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires local access to the hypervisor host or to a guest VM running on a hypervisor with NVIDIA vGPU software installed and the Virtual GPU Manager active. The attacker must hold at minimum a low-privileged account (PR:L per CVSS vector - unauthenticated remote exploitation is not possible). High attack complexity (AC:H) indicates exploitation is not straightforward and likely depends on specific memory state or timing conditions within the vGPU Manager process. The affected deployment mode is specifically virtualized GPU environments using NVIDIA vGPU software - bare-metal NVIDIA GPU deployments without the vGPU Manager component are not affected by this CVE. Standard standalone workstation or server GPU driver installations are outside the blast radius. Exploitation is not automatable per SSVC, meaning mass-scanning or worm-style exploitation is not a realistic threat vector. |
| Impact | Multiple signals converge to indicate moderate-to-low immediate exploitation priority. The CVSS base score of 5.8 (Medium) is consistent with local-only access (AV:L), high attack complexity (AC:H), and mixed impact (C:L/I:L/A:H). The high availability impact is the most significant concern - a successful exploit could crash or destabilize the vGPU Manager on the host, affecting all guest VMs sharing the GPU. EPSS at 0.01% (2nd percentile) reflects very low community-observed exploitation probability. SSVC corroborates this: Exploitation status is none, Automatable is no (high complexity precludes automated mass exploitation), and Technical Impact is partial. There is no KEV listing and no public POC at time of analysis. Despite a relatively low CVSS score, environments running vGPU in multi-tenant or cloud hosting contexts face a meaningful confidentiality and availability risk because a compromised guest VM could potentially leverage this to impact co-resident tenants via the shared host manager. No signal conflict identified between CVSS vector and description - both imply a local-access prerequisite. |
| Exploit ScenarioDerived | An attacker with a low-privileged account on a guest VM or on the hypervisor host crafts a malformed request or IOCTL sequence targeting the NVIDIA Virtual GPU Manager's input-handling routines, deliberately triggering an out-of-bounds write in host memory. The memory corruption may crash the vGPU Manager process - taking down GPU access for all co-resident guest VMs - or, under favorable memory layout conditions, may corrupt adjacent data structures to leak or modify sensitive information. No public proof-of-concept exists at time of analysis, and the high attack complexity (AC:H) means reliable exploitation requires precise knowledge of memory layout and timing. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 08, 2026
Out-of-bounds write in NVIDIA Virtual GPU Manager exposes virtualized GPU deployments to denial of service, data tampering, and information disclosure. A local, low-privileged attacker operating within a virtualized environment can trigger the memory corruption flaw in the host-side vGPU manager component across multiple affected driver branches (vGPU 16.x through 20.x). No public exploit code exists at time of analysis, and EPSS probability is at the 2nd percentile, but the high availability impact (A:H in CVSS) and the prevalence of vGPU in enterprise virtualization infrastructure warrant prompt patching.
RemediationAI
The primary remediation is to upgrade NVIDIA Virtual GPU Manager to a version beyond the affected ranges documented in EUVD-2026-31935. Consult the NVIDIA Product Security advisory at https://nvidia.custhelp.com/app/answers/detail/a_id/5821 for exact patched build numbers per driver branch, as the provided data confirms affected-through versions but does not enumerate explicit fixed release identifiers. For deployments that cannot patch immediately, compensating controls include restricting access to the vGPU-enabled host to trusted, explicitly authorized users only - reducing the pool of potential local attackers - and enabling hypervisor-level monitoring for anomalous vGPU Manager process behavior or unexpected crashes. Given AV:L and PR:L, network-level controls alone are insufficient; access to guest VMs or the hypervisor host itself must be hardened. Note that restricting guest VM user privileges may introduce operational friction in VDI or ML workload environments. No workaround that eliminates the vulnerability without patching has been identified from available data.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
NVIDIA Virtual GPU Manager (vGPU Manager) is a host-side software component that mediates GPU resource sharing across virtual machines in VMware vSphere, Citrix Hypervisor, and KVM-based environments. CWE-787 (Out-of-bounds Write) is the root cause - attacker-controlled input causes the manager process to write beyond the allocated buffer boundary, corrupting adjacent memory. This class of bug typically arises in parsing or handling of guest-initiated requests or driver IOCTLs. The CPE string cpe:2.3:a:nvidia:virtual_gpu_manager:*:*:*:*:*:*:*:* confirms the flaw is in the vGPU Manager application layer rather than the bare-metal NVIDIA display driver. Tags confirm Memory Corruption and Buffer Overflow characteristics consistent with CWE-787. The CVSS vector AV:L/AC:H/PR:L indicates the attacker must have a foothold inside the host or guest environment, and exploitation requires a specific, reproducible set of conditions (AC:H), elevating the difficulty beyond commodity exploitation.
Know when Virtual Gpu Manager 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:H/PR:L/UI:N/S:U/C:L/I:L/A:H
Primary rating from Vendor (nvidia) · only source for this CVE.
CVSS VectorVendor: nvidia
DescriptionCVE.org
NVIDIA vGPU software contains a vulnerability in the virtual GPU manager, where an attacker could cause an out-of-bound access. A successful exploit of this vulnerability might lead to data tampering, denial of service, or information disclosure.
Threat Intelligence Overview
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
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
More in Virtual Gpu Manager
View allLocal privilege escalation and code execution in the NVIDIA Display Driver for Linux (GeForce, RTX/Quadro/NVS, Tesla, an
An out-of-bounds read in the kernel-mode layer of NVIDIA GPU Display Driver on Windows and Linux allows a local, authent
Local privilege escalation and potential code execution in NVIDIA GPU Display Driver for Windows and Linux arise from a
Local privilege escalation in the kernel-mode layer of the NVIDIA GPU Display Driver for Linux allows an unprivileged lo
Privilege escalation in NVIDIA's GPU Display Driver for Windows lets a local, low-privileged authenticated user bypass a
Local privilege escalation in NVIDIA Display Driver for Linux (GeForce, RTX/Quadro/NVS, Tesla, and Virtual GPU Manager b
Local privilege escalation in NVIDIA Display Driver for Windows (GeForce, RTX/Quadro/NVS, Tesla, and vGPU guest/manager
Incorrect resource transfer between spheres in the NVIDIA vGPU Virtual GPU Manager for Linux allows a locally positioned
An out-of-bounds write in the kernel-mode layer of NVIDIA vGPU Virtual GPU Manager for Linux lets a local attacker with
Local privilege escalation, code execution, denial of service, and information disclosure affect Linux hosts running NVI
Local privilege escalation in NVIDIA vGPU Virtual GPU Manager for Linux stems from an out-of-bounds read in firmware (CW
Local attackers with low privileges on a Linux host running NVIDIA vGPU Virtual GPU Manager can trigger an out-of-bounds
EUVD-2026-31935
GHSA-5jr9-f23j-wrrp
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB