What is the CVSS score of CVE-2026-24200?

CVE-2026-24200 has a CVSS 3.1 base score of 7.0 (High). CVSS vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.0%.

Which versions of NVIDIA vGPU Manager are affected by CVE-2026-24200?

NVIDIA Virtual GPU Manager (versions 16.x-20.x) contains a local privilege escalation vulnerability in the vGPU hypervisor allowing authenticated local attackers to execute arbitrary code and…

How to fix or mitigate CVE-2026-24200?

Within 24 hours: Identify all NVIDIA vGPU deployments currently running versions 16.x through 20.x and assess exposure scope. Within 7 days: Enforce local access controls limiting administrative privileges on vGPU hosts, implement privilege escalation detection and logging, and segregate affected systems by security zone. Within 30 days: Establish alert on NVIDIA security advisories and prepare deployment strategy for vGPU hypervisor patches upon vendor release.

NVIDIA vGPU Manager CVE-2026-24200

EUVD-2026-31934 HIGH

Use After Free (CWE-416)

2026-05-26 nvidia

GHSA-mp9c-jx49-947f

Nvidia Memory Corruption RCE Information Disclosure Use After Free Denial Of Service Virtual Gpu Manager

7.0

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

7.0 HIGH

AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector

Local

Attack Complexity

High

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Jun 08, 2026 - 09:37 vuln.today

DescriptionCVE.org

NVIDIA vGPU software contains a vulnerability in the virtual GPU manager, where an attacker could cause a use-after-free for stack memory. A successful exploit of this vulnerability might lead to denial of service, escalation of privileges, information disclosure, data tampering, and code execution.

AnalysisAI

Local privilege escalation and code execution in NVIDIA Virtual GPU Manager arises from a use-after-free on stack memory within the vGPU hypervisor component. Authenticated local attackers on the host or guest side of an affected vGPU deployment (vGPU branches 16.x through 20.x) can trigger memory corruption that may yield DoS, info disclosure, data tampering, or arbitrary code execution. No public exploit identified at time of analysis and EPSS is 0.01%, but SSVC rates technical impact as total.

Technical ContextAI

NVIDIA Virtual GPU Manager is the host-side hypervisor component (typically loaded as a kernel/VMM module on ESXi, KVM, Citrix Hypervisor, or Nutanix AHV) that mediates partitioning of physical NVIDIA GPUs into multiple vGPU instances assigned to guest VMs. The flaw is classified CWE-416 (Use After Free), specifically against a stack-allocated object - meaning a freed reference is dereferenced after its lifetime ends, allowing controlled reuse of that memory region. Because the manager runs at hypervisor privilege and the affected CPEs all point at cpe:2.3:a:nvidia:virtual_gpu_manager, successful corruption directly threatens VM isolation and host integrity.

RemediationAI

Patch available per vendor advisory - apply the fixed vGPU Manager driver branches published in NVIDIA security bulletin 5821 (https://nvidia.custhelp.com/app/answers/detail/a_id/5821); exact post-fix version strings were not independently confirmed from the supplied data, so consult the bulletin for the patched build that supersedes 535.288.01 (16.x), 580.126.08/582.16 (19.4), 595.94 (20.0), and 595.58.02 (March 2026). Until hypervisor hosts can be drained and rebooted into the patched driver, compensating controls include restricting which tenants/admins can obtain low-privilege execution on hosts running vGPU Manager, segregating high-trust and low-trust workloads onto separate GPU hosts (side effect: capacity fragmentation), and disabling vGPU profiles on hosts that do not require GPU sharing in favor of GPU passthrough (side effect: loss of multi-tenant density). Cross-reference https://vuldb.com/vuln/365767 and https://www.cve.org/CVERecord?id=CVE-2026-24200 for tracking.