CVE-2025-23266 — nvidia-container-toolkit
CRITICALCVE-2025-23266 is a critical-severity (CVSS 9) CWE-426 vulnerability in github.com/NVIDIA/nvidia-container-toolkit. 1 public exploit reference exists, 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
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
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2025-23266 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,636 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
github.com/NVIDIA/nvidia-container-toolkit🐹github.com/NVIDIA/k8s-device-plugin🐹github.com/NVIDIA/gpu-operator🐹github.com/NVIDIA/mig-partedReal-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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/NVIDIA/nvidia-container-toolkit | all versions | 1.17.8go get github.com/NVIDIA/nvidia-container-toolkit@v1.17.8 |
| 🐹Go | github.com/NVIDIA/k8s-device-plugin | all versions | 0.17.3go get github.com/NVIDIA/k8s-device-plugin@v0.17.3 |
| 🐹Go | github.com/NVIDIA/gpu-operator | all versions | 25.3.2go get github.com/NVIDIA/gpu-operator@v25.3.2 |
| 🐹Go | github.com/NVIDIA/mig-parted | all versions | 0.12.2go get github.com/NVIDIA/mig-parted@v0.12.2 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
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.
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.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-23266 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2025-23266. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
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.
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…
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Enterprise Linux 10 | toolbox-0:0.2-1.el10_0 | RHSA-2025:13674 |
| Red Hat Enterprise Linux 9 | toolbox-0:0.2-1.el9_6 | RHSA-2025:13673 |
Frequently Asked Questions
Is CVE-2025-23266 in your dependencies?
O3 Security finds CVE-2025-23266 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.