# CVE-2026-47502: Integer overflow in GeForce

> A guest user can exploit an integer overflow in the NVIDIA vGPU kernel driver to achieve code execution, privilege escalation, and data tampering.

- **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:** Yes
- **Published:** 30 Sep 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-7rjr-4wj7-h49g

## What is CVE-2026-47502?

CVE-2026-47502 is a high-severity vulnerability in NVIDIA GeForce, 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 Windows and Linux contains a vulnerability in the kernel mode layer, where a guest user could cause an integer overflow leading to memory corruption. A successful exploit of this vulnerability might lead to code execution, denial of service, escalation of privileges, information disclosure, and data tampering.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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


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

Apply the vendor's patch.

## Is CVE-2026-47502 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-47502 is a high-severity vulnerability in NVIDIA GeForce, 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-47502 in the wild and no public exploit code.

Affected product: NVIDIA GeForce. 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-47502/ (Markdown: https://insights.sbomify.com/CVE-2026-47502/index.md)
```

## Sources

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

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