Skip to content
Fencer Intel
high 7.0

CVE-2026-24200 json

NVIDIA vGPU software contains a vulnerability in the virtual GPU manager, where an attacker could cause a use-after-free for stack memory.

published 5mo ago modified 3mo ago also EUVD-2026-31934

cvss
7.0
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 6%
public exploits
0
none known

Summary

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.

Patch / fix

  • nvidia virtual_gpu_manager 16.14, 19.5, 20.1
  • nvidia geforce 535.309.01, 539.72, 580.159.03, 582.53, 595.71.05, 596.36
  • nvidia gpu_driver 535.309.01, 539.72, 580.159.03, 582.53, 595.71.05, 596.36
  • nvidia tesla 535.309.01, 539.72, 580.159.03, 582.53, 595.71.05, 596.36

Is CVE-2026-24200 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
5mo ago

Exploit prediction

0.17% chance of exploitation in the next 30 days, higher than 6% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 7.0 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected products

  • NVIDIA Virtual GPU Manager

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.