Skip to content
Breach Index · running record

NVIDIA vulnerabilities in 2026: ForgePtr, CVE-2026-47501 (not a breach of NVIDIA)

NVIDIA's GPU drivers run on most AI training and inference clusters, so a flaw in the driver's kernel code reaches every container and tenant that shares a GPU node. This page tracks ForgePtr and keeps NVIDIA's bulletin apart from what the researchers who named it say.

Short answer

Was NVIDIA hacked?

No, ForgePtr is not a breach of NVIDIA: nothing reported shows an intrusion at NVIDIA. It is a vulnerability in NVIDIA's GPU display driver for Linux. NVIDIA's September 2026 bulletin, published 30 September, lists CVE-2026-47501 as an out-of-bounds write in the kernel-mode layer (CVSS 3.1 7.8, High), fixed in 580.178.04, 595.91.07, 610.57.04 and 615.71.09, and in vGPU 19.6 and 20.2.

Stealthium, which named the flaw ForgePtr, says an unprivileged process in a container with only GPU access can use it to get root on the host. It released no proof of concept. CVE-2026-47501 was not in CISA's Known Exploited Vulnerabilities catalog on 19 November 2026, and we found no report of exploitation in the wild.

Separately, on 18 November 2026 the ransomware group The Gentlemen named NVIDIA on its leak site, with no data shown and a countdown to 28 November. That is an unverified claim: NVIDIA has not confirmed a breach, and told BleepingComputer and SecurityWeek it is investigating an incident that "may have affected a third-party partner" and has "found no indication that NVIDIA systems or networks were affected."

Timeline at a glance

  1. 9 Sep 2026NVIDIA releases Linux driver 615.71.09, which Stealthium says adds the missing check. (Stealthium)Not a breach
  2. 30 Sep 2026NVIDIA bulletin: CVE-2026-47501 (CVSS 7.8) fixed in 580.178.04, 595.91.07, 610.57.04, 615.71.09 and vGPU 19.6 / 20.2. (NVIDIA)Not a breach
  3. Nov 2026Stealthium publishes ForgePtr: container-to-host root on shared GPU nodes, no proof of concept released. (Stealthium)Reported
  4. 18-19 Nov 2026The Gentlemen name NVIDIA on their leak site (no data shown, countdown to 28 Nov). NVIDIA: investigating a possible third-party partner incident, no indication its systems were affected. (BleepingComputer; SecurityWeek)Unverified claim

Last updated 19 November 2026. Every entry is dated and linked to its source; claims by attackers are labelled as claims, never stated as fact.

NVIDIA incident timeline, in detail

Confirmed = acknowledged by NVIDIA, a regulator filing or a court. Reported = credible reporting NVIDIA has not fully confirmed. Unverified claim = an attacker or leak-site claim.

Sep-Nov 2026Not a breachProduct vulnerability (local privilege escalation)

ForgePtr (CVE-2026-47501): kernel write in the Linux GPU driver, container to host root

What happened. NVIDIA describes an out-of-bounds write (CWE-787) in the Linux driver's kernel-mode layer when a user supplies "mismatched memory buffers during event buffer setup", CVSS 3.1 7.8 (AV:L/AC:L/PR:L/UI:N). Fixed for GeForce, NVIDIA RTX/Quadro/NVS and Tesla in 580.178.04 (R580), 595.91.07 (R595), 610.57.04 (R610) and 615.71.09 (R615); vGPU in 19.6 and 20.2. Stealthium says the bug has been in the open GPU kernel modules since their first release, 515.43.04, in May 2022.

Impact. Stealthium says an unprivileged local user, with a separate kernel address leak, can write chosen bytes into kernel memory, overwrite core_pattern to run a program as host root from inside a container, and switch off kernel lockdown and module signing. It says there is no workaround short of patching. Not in CISA KEV on 19 November 2026; no exploitation reported.

Sources: NVIDIA bulletin 5861 · Stealthium: ForgePtr · CISA KEV

Where the reports disagree

  • R610 fix: NVIDIA lists 610.57.04 as the fixed R610 driver; Stealthium says the flaw is present through 610.57.04 and that it got root on that version, and advises 615.71.09 or later. Neither document addresses the other.
  • Credit: Stealthium says its researcher Branislav Brzak found the flaw and reported it to NVIDIA. NVIDIA's bulletin lists no acknowledgement for CVE-2026-47501 and says unacknowledged CVEs were found internally.
  • Closed driver: NVIDIA's bulletin covers the Linux driver without splitting open and proprietary kernel modules. Stealthium traced the flaw in the open modules and says it "likely" predates open-sourcing in the closed driver, which is an inference.

The pattern across the record

The GPU driver is part of the isolation boundary

On a shared GPU node, every container talks to the same kernel driver. A write primitive in that driver defeats container namespaces, seccomp and Pod Security settings, so driver patch level decides tenant isolation.

Vulnerabilities are not breaches

Nothing reported shows an intrusion at NVIDIA. The exposure is to organisations that run affected drivers on hosts shared by users or containers they do not fully trust.

What it means for NVIDIA customers — and what to do

If you run NVIDIA GPUs on Linux, the question is your driver version and who else can run code on the same node, not whether NVIDIA was breached.

  1. 1.Inventory driver versions

    Run nvidia-smi or read /proc/driver/nvidia/version on every GPU node, including Kubernetes GPU pools, research clusters, GPU CI runners and vGPU hosts and guests.

  2. 2.Patch shared nodes first

    Move multi-tenant and shared GPU nodes to a fixed driver first (615.71.09 or later where you can, given the R610 disagreement), through the node image or driver container if that is how drivers are delivered.

    What to do this week
  3. 3.Keep untrusted workloads off unpatched nodes

    Until patched, use taints, dedicated node pools or VM isolation for tenants you do not trust. Stealthium says no sysctl or seccomp profile closes the flaw.

  4. 4.Set the deadline with data

    Score it with SSVC and re-check KEV.

    SSVC calculator
Take this with you
Incident timeline · What NVIDIA customers should do · Sources

CISO takeaways

Sources

Company statements and regulator filings first, then reputable reporting. Reviewed 19 November 2026.

  1. 1.Security Bulletin: NVIDIA GPU Display Driver, September 2026 (a_id 5861) — NVIDIA, 30 Sep 2026
  2. 2.Your Configs, My Choices: Introducing ForgePtr — Stealthium, Nov 2026
  3. 3.Known Exploited Vulnerabilities catalog (checked: not listed) — CISA, 18 Nov 2026
  4. 4.NVIDIA investigating Gentlemen ransomware breach claims — BleepingComputer, 19 Nov 2026

Frequently asked questions

Was NVIDIA hacked?

No breach of NVIDIA is confirmed. ForgePtr (CVE-2026-47501) is a vulnerability in NVIDIA's Linux GPU driver, fixed in September 2026. Separately, The Gentlemen named NVIDIA on their leak site on 18 November 2026; that is an unverified claim, and NVIDIA says it has found no indication its systems or networks were affected.

Which NVIDIA drivers fix ForgePtr?

NVIDIA lists 580.178.04, 595.91.07, 610.57.04 and 615.71.09 on Linux, and vGPU 19.6 and 20.2. Stealthium says 610.57.04 is still affected and advises 615.71.09 or later.

Is ForgePtr exploited?

We found no report of exploitation in the wild, and it was not in CISA KEV on 19 November 2026. Stealthium built a working exploit but has not released it.

Is there a workaround?

Stealthium says no: no sysctl or seccomp profile closes it. Patch, and keep untrusted workloads off unpatched GPU nodes until then.

Our coverage of NVIDIA

Same sourced, verification-tagged timeline, company by company — compare how peers have fared.

Or see the full Breach Index and how to read it.

Independent analysis for security-leadership education; not affiliated with or endorsed by NVIDIA. Facts are attributed to the dated sources above, and anything disputed or unconfirmed is labelled as such. See the full Breach Index.