NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
CRITICAL severity

CVE-2025-23266 — nvidia-container-toolkit

CRITICAL

CVE-2025-23266 is a critical-severity (CVSS 9) CWE-426 vulnerability in github.com/NVIDIA/nvidia-container-toolkit. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for github.com/NVIDIA/nvidia-container-toolkit — see the affected versions and patch details below.

NVIDIA Container Toolkit for all platforms contains an Untrusted Search Path

Also known asGO-2025-3992
Published
Updated
Affected
4 pkgs
Patched
4 / 4
Exploits
1 known
Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • A successful exploit gives an attacker total control of the affected component, not partial access.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-23266.

EPSS Exploitation Probability

via FIRST.org ↗
3.3%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs89th percentile — riskier than 89% of all scored CVEsHighest risk
0.00%1.43%2.87%4.30%0.1%3.3%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

4 pkgs affected
🐹github.com/NVIDIA/nvidia-container-toolkit🐹github.com/NVIDIA/k8s-device-plugin🐹github.com/NVIDIA/gpu-operator🐹github.com/NVIDIA/mig-parted

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

NVIDIA Container Toolkit for all platforms contains a vulnerability in some hooks used to initialize the container, where an attacker could execute arbitrary code with elevated permissions. A successful exploit of this vulnerability might lead to escalation of privileges, data tampering, information disclosure, and denial of service.

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/NVIDIA/nvidia-container-toolkitall versions1.17.8go get github.com/NVIDIA/nvidia-container-toolkit@v1.17.8
🐹Gogithub.com/NVIDIA/k8s-device-pluginall versions0.17.3go get github.com/NVIDIA/k8s-device-plugin@v0.17.3
🐹Gogithub.com/NVIDIA/gpu-operatorall versions25.3.2go get github.com/NVIDIA/gpu-operator@v25.3.2
🐹Gogithub.com/NVIDIA/mig-partedall versions0.12.2go get github.com/NVIDIA/mig-parted@v0.12.2
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

jpts/cve-2025-23266-poc

PoC for NVIDIAScape bug

⭐ 14🍴 6Jul 2026

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/NVIDIA/nvidia-container-toolkit, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update github.com/NVIDIA/nvidia-container-toolkit to 1.17.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-23266 is resolved across your whole dependency graph.

  3. Workarounds

    Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

RHEL AI is not affected because it uses CDI mode with NVIDIA Container Toolkit versions later than 1.17.5, which are not vulnerable, and does not rely on the enable-cuda-compat hook, thereby eliminating the attack vector entirely. This vulnerability is marked as Important rather than Critical primarily due to its…

Workaround published by Red Hat
No mitigation is currently available that meets Red Hat Product Security’s standards for usability, deployment, applicability, or stability.
Source: Red Hat security advisory for CVE-2025-23266 (CC BY 4.0)
ProductFixed inAdvisory
Red Hat Enterprise Linux 10toolbox-0:0.2-1.el10_0RHSA-2025:13674
Red Hat Enterprise Linux 9toolbox-0:0.2-1.el9_6RHSA-2025:13673

Frequently Asked Questions

NVIDIA Container Toolkit for all platforms contains a vulnerability in some hooks used to initialize the container, where an attacker could execute arbitrary code with elevated permissions. A successful exploit of this vulnerability might lead to escalation of privileges, data tampering, information disclosure, and denial of service.
O3 Security · Impact-Aware SCA

Is CVE-2025-23266 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2025-23266: nvidia-container RCE — Fixed in 1.17.8