# CVE-2026-47513: Memory corruption in GeForce

> A local attacker can exploit an out-of-bounds read in the NVIDIA GPU driver kernel layer to execute code, escalate privileges, or disclose information.

- **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:** DEBIAN-CVE-2026-47513, GHSA-3395-fqvp-xv55, UBUNTU-CVE-2026-47513

## What is CVE-2026-47513?

CVE-2026-47513 is a high-severity memory corruption 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 GPU Display Driver for Windows and Linux contains a vulnerability in the kernel mode layer, where a user could cause an out-of-bounds read from kernel heap memory. 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-47513?


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

Apply the vendor's patch.

## Is CVE-2026-47513 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-47513 is a high-severity memory corruption 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-47513 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-47513/ (Markdown: https://insights.sbomify.com/CVE-2026-47513/index.md)
```

## Sources

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

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