NVIDIA Container Toolkit and NVIDIA GPU Operator for Linux contain a UNIX vulnerability where a specially crafted container image can lead t
Noroxi assessment
Priority: Monitor (action score 16/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.39% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: Azure Linux 3.0 ARM 1.17.1-1; Azure Linux 3.0 x64 1.17.1-1; CBL Mariner 2.0 ARM 1.17.1-1.
Low priority for now. Upgrade to Azure Linux 3.0 ARM 1.17.1-1; Azure Linux 3.0 x64 1.17.1-1; CBL Mariner 2.0 ARM 1.17.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
NVIDIA Container Toolkit and NVIDIA GPU Operator for Linux contain a UNIX vulnerability where a specially crafted container image can lead to the creation of unauthorized files on the host. The name and location of the files cannot be controlled by an attacker. A successful exploit of this vulnerability might lead to data tampering.
- Published
- Nov 5, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.3% · 31th percentile
- CWE
- CWE-61
Report tools
Action score
16
Monitor
Low priority for now.
- CVSS
- 16 / 40 · 4.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 4.1
- CNA · nvidia
- 4.1
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| nvidia | nvidia container toolkit | cpe:2.3:a:nvidia:nvidia_container_toolkit |
| nvidia | nvidia gpu operator | cpe:2.3:a:nvidia:nvidia_gpu_operator |
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- nvidia nvidia container toolkitbefore 1.17
- nvidia nvidia gpu operatorbefore 24.9.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (nvidia). Independent of NVD's CPE analysis and usually ahead of it.
NVIDIA NVIDIA Container Toolkit
- All versions up to and including v1.16.2affected
NVIDIA NVIDIA GPU Operator
- All versions up to and including 24.6.2affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| openSUSE:Leap 15.6 | nvidia-container-toolkit | before 1.18.0-150200.5.17.1 | 1.18.0-150200.5.17.1 |
| SUSE:Linux Enterprise Module for Containers 15 SP6 | nvidia-container-toolkit | before 1.18.0-150200.5.17.1 | 1.18.0-150200.5.17.1 |
Same product
nvidia: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-0132NVIDIA Container Toolkit 1.16.1 or earlier contains a Time-of-check Time-of-Use (TOCTOU) vulnerability when used with default configuration 45Plan
- CVE-2025-23359NVIDIA Container Toolkit for Linux contains a Time-of-Check Time-of-Use (TOCTOU) vulnerability when used with default configuration, where a33Monitor
- CVE-2024-0136NVIDIA Container Toolkit contains an improper isolation vulnerability where a specially crafted container image could lead to untrusted code33Monitor
Published before and after this one in the same product
- ← EarlierCVE-2024-0133Sep 26, 2024 · NVIDIA Container Toolkit 1.16.1 or earlier contains a vulnerability in the default mode of operation allowing a specially crafted container 13Monitor
- Later →CVE-2024-0135Jan 27, 2025 · NVIDIA Container Toolkit contains an improper isolation vulnerability where a specially crafted container image could lead to modification o30Monitor
- Later →CVE-2024-0137Jan 27, 2025 · NVIDIA Container Toolkit contains an improper isolation vulnerability where a specially crafted container image could lead to untrusted code26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Azure Linux 3.0 ARM | 1.17.1-1 · nvidia-container-toolkit | Microsoft (MSRC) |
| Azure Linux 3.0 x64 | 1.17.1-1 · nvidia-container-toolkit | Microsoft (MSRC) |
| CBL Mariner 2.0 ARM | 1.17.1-1 · nvidia-container-toolkit | Microsoft (MSRC) |
| CBL Mariner 2.0 x64 | 1.17.1-1 · nvidia-container-toolkit | Microsoft (MSRC) |
| opensuse:nvidia-container-toolkit | 1.18.0-150200.5.17.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| suse:nvidia-container-toolkit | 1.18.0-150200.5.17.1 · SUSE:Linux Enterprise Module for Containers 15 SP6 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
- NVIDIA Public Bug BountyIntigriti · paid · up to $15,000
- NVIDIA Vulnerability Disclosure ProgramIntigriti · disclosure only (VDP)
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- low · data or configuration can be modified
- Availability
- none
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality impact
- None
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-61 · UNIX Symbolic Link (Symlink) FollowingCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:N/I:L/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.