# CVE-2026-47521: Memory corruption in Virtual GPU Manager

> An out-of-bounds read in NVIDIA vGPU Manager allows attackers to execute code, escalate privileges, cause denial of service, or disclose and tamper with data.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Sep 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-6qvj-xgrp-j42v

## What is CVE-2026-47521?

CVE-2026-47521 is a high-severity memory corruption vulnerability in NVIDIA Virtual GPU Manager, published on 30 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

NVIDIA vGPU Virtual GPU Manager for Linux contains a vulnerability in the kernel mode layer where an attacker could cause an out-of-bounds read. A successful exploit of this vulnerability might lead to code execution, denial of service, escalation of privileges, information disclosure, and data tampering.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2026-47521?


## How do I fix CVE-2026-47521?

No fix has been published for CVE-2026-47521 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-47521 being exploited?

There is no known exploitation of CVE-2026-47521 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-47521 and fix it if it is affected.

What it is: CVE-2026-47521 is a high-severity memory corruption vulnerability in NVIDIA Virtual GPU Manager, published on 30 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-47521 in the wild and no public exploit code.

Affected product: NVIDIA Virtual GPU Manager. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-47521/ (Markdown: https://insights.sbomify.com/CVE-2026-47521/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-47521
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-47521
- OSV: https://osv.dev/vulnerability/CVE-2026-47521

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-47521/
Summaries are generated and may contain mistakes; the official description above is the record.