Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2024-0132: TOCTOU Container Escape in NVIDIA Container Toolkit

Published Sep 26, 2024 · Updated 3 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS8.3High · v3.1
EPSS40.8%99th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
NVIDIA Corporation
IdentifiersCVE-2024-0132CWE-367 · Time-of-check Time-of-use (TOCTOU)…

CVE-2024-0132 is a time-of-check/time-of-use vulnerability affecting NVIDIA Container Toolkit through version 1.16.1 and NVIDIA GPU Operator through version 24.6.1 on Linux in the default configuration. Unsafe symbolic-link resolution while processing container-provided library paths during initialization allows a specially crafted container image to redirect privileged host-side toolkit operations to the host filesystem. Successful exploitation can escape container isolation and potentially lead to host-root code execution, information disclosure, data tampering, and denial of service. Container Device Interface (CDI) use cases are not affected by this vulnerability. The vulnerability has a CVSS v3.1 base score of 9.0.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Exploitation can initially expose the host filesystem for reading, compromising host secrets, application data, proprietary AI models, and information belonging to other workloads. Access to host container-runtime Unix sockets can turn this filesystem exposure into arbitrary command execution as root and complete host compromise; a read-only filesystem mount does not prevent interaction with those sockets. Additional consequences include privilege escalation, data modification, and service disruption. In shared GPU and Kubernetes environments, compromise can cross tenant boundaries and potentially support lateral movement using exposed credentials or runtime access.

Mitigation

If you can’t patch tonight, do this now.

Use CDI-based GPU integration where feasible, since CDI use cases are not affected by CVE-2024-0132. Until updates are deployed, restrict execution of externally supplied or untrusted GPU container images through image admission controls and approved-image policies. Restrict container-runtime API access and unnecessary host filesystem or socket exposure. Monitor privileged toolkit activity and unexpected container-to-host filesystem access as supplementary detection measures, not substitutes for patching.

Remediation

Patch, then assume compromise.

NVIDIA released initial fixes in NVIDIA Container Toolkit 1.16.2 and NVIDIA GPU Operator 24.6.2; replace affected installations and update GPU worker-node images. For affected AWS deployments, the initial remediation was to use ECS/EKS GPU-optimized AMIs containing Container Toolkit 1.16.2 or later, or Bottlerocket 1.24.0 or later. Subsequent research identified an incomplete fix tracked separately as CVE-2025-23359, so the original minimum fixed versions should not be treated as sufficient protection against related bypasses. Deploy current vendor-supported releases addressing the original vulnerability and subsequent bypasses, and verify the toolkit version actually installed on each node.

Public exploits

Exploits

2 exploits validated by Mallory's analysis. Hidden: 2 rejected by Mallory's analysis as not a working exploit; 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
poc-cve-2024-0132This repository is a proof-of-concept (PoC) exploit for CVE-2024-0132, targeting NVIDIA's nvidia-container-toolkit on Linux systems. The exploit demonstrates how a malicious container, when run with the NVIDIA runtime and GPU access, can escape its isolation and access files from the host filesystem and interact with the host's Docker daemon via the docker.sock UNIX socket. The repository contains multiple versions (v0.1, v0.2, v0.3), each with a Dockerfile and an entrypoint.sh script. The exploit works by creating symlinks within the container that point to host directories, then using these to read sensitive files (e.g., /etc/hostname) and communicate with the Docker daemon. The main payload is a bash script executed as the container's entrypoint. The PoC is operational and demonstrates real host compromise potential, but does not include weaponized or automated post-exploitation features. The README provides detailed setup and reproduction steps, including environment requirements and affected versions.ssst0n3 · Disclosed Oct 15, 2024 · bash · dockerfile · containerPoCCVE-2024-0132This repository provides a proof-of-concept (PoC) exploit for CVE-2024-0132, a TOCTOU (Time-of-Check to Time-of-Use) vulnerability in the NVIDIA container toolkit (libnvidia-container) on Linux systems. The exploit is implemented as a Dockerfile that sets up a specific directory and symlink structure to abuse the way the toolkit mounts libraries from /usr/local/cuda/compat/ into the container. By carefully crafting directories and symlinks, the PoC demonstrates how an attacker could trick the mounting logic into mounting arbitrary host files or directories into the container, potentially leading to privilege escalation or access to sensitive host data. The repository contains two files: a Dockerfile with the exploit logic and a README.md that explains the vulnerability, the exploit steps, and references to the relevant code in the NVIDIA toolkit. The exploit is local in nature, requiring the ability to build and run Docker containers with the NVIDIA toolkit.r0binak · Disclosed Dec 20, 2024 · Dockerfile · localPoC
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
NVIDIA CorporationContainer Toolkitapplication
NVIDIA CorporationGpu Operatorapplication
NVIDIA CorporationNvidia Container Toolkitapplication
NVIDIA CorporationNvidia Gpu Operatorapplication
FAQ

Frequently asked questions

Is CVE-2024-0132 exploited in the wild?
As of Nov 19, 2026, Mallory has no reports of CVE-2024-0132 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2024-0132?
Yes. Mallory tracks 2 public exploits or proofs of concept for CVE-2024-0132, the earliest disclosed Oct 15, 2024.
Is there a patch for CVE-2024-0132?
NVIDIA released initial fixes in NVIDIA Container Toolkit 1.16.2 and NVIDIA GPU Operator 24.6.2; replace affected installations and update GPU worker-node images. For affected AWS deployments, the initial remediation was to use ECS/EKS GPU-optimized AMIs containing Container Toolkit 1.16.2 or later, or Bottlerocket 1.24.0 or later.
What products are affected by CVE-2024-0132?
NVIDIA Corporation Container Toolkit, NVIDIA Corporation Gpu Operator, NVIDIA Corporation Nvidia Container Toolkit, and NVIDIA Corporation Nvidia Gpu Operator.
How severe is CVE-2024-0132?
CVE-2024-0132 has a CVSS v3.1 score of 8.3 (High) and an EPSS score of 40.8% (99th percentile) as of Nov 19, 2026.
Activity feed

Recent activity

23 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+7 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity11Community discussion across Reddit, Mastodon, and other social sources.