CVE-2024-0132 — nvidia-container-toolkit
CRITICALCVE-2024-0132 is a critical-severity (CVSS 9) CWE-367 vulnerability in github.com/NVIDIA/nvidia-container-toolkit. 3 public exploit or proof-of-concept references are 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 contains a Time-of-check Time-of-Use (TOCTOU) vulnerability
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-2024-0132.
EPSS Exploitation Probability
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
github.com/NVIDIA/nvidia-container-toolkitReal-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 1.16.1 or earlier contains a Time-of-check Time-of-Use (TOCTOU) vulnerability when used with default configuration where a specifically crafted container image may gain access to the host file system. This does not impact use cases where CDI is used. A successful exploit of this vulnerability may lead to code execution, denial of service, escalation of privileges, information disclosure, and data tampering.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/NVIDIA/nvidia-container-toolkit | all versions | 1.16.2go get github.com/NVIDIA/nvidia-container-toolkit@v1.16.2 |
Affected Products
nvidia container toolkitnvidianvidia gpu operatornvidiaResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
NVIDIA Container Toolkit 1.16.1 - Time-of-check Time-of-Use (TOCTOU)
by r0binak · Mar 26, 2025
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.16.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-0132 is resolved across your whole dependency graph.
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.
No Red Hat containers are vulnerable because they all implement CDI. Due to specific prerequisites, this vulnerability in the NVIDIA Container Toolkit does not affect Red Hat Products and is rated as Important severity rather than Critical. First, a specifically crafted container image is required for effective…
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.Source: Red Hat security advisory for CVE-2024-0132 (CC BY 4.0)
Frequently Asked Questions
Is CVE-2024-0132 in your dependencies?
Find it across Go, including transitive dependencies.