# CVE-2025-23359: Race condition in Container Toolkit

> A crafted container image can exploit a race condition to access the host file system, leading to code execution and privilege escalation.

- **Severity:** High 8.3 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 12 Feb 2025
- **Updated:** 11 Apr 2025
- **Also known as:** AZL-56852, AZL-56857, GHSA-4hmh-pm5p-9j7j

## What is CVE-2025-23359?

CVE-2025-23359 is a high-severity vulnerability in NVIDIA Container Toolkit, published on 12 Feb 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

NVIDIA Container Toolkit for Linux contains a Time-of-Check Time-of-Use (TOCTOU) vulnerability when used with default configuration, where a crafted container image could gain access to the host file system. A successful exploit of this vulnerability might lead to code execution, denial of service, escalation of privileges, information disclosure, and data tampering.

Weakness: CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition)

## Which versions are affected by CVE-2025-23359?

It affects 2 products.


Products: Nvidia Nvidia Container Toolkit, Nvidia Nvidia Gpu Operator.

## How do I fix CVE-2025-23359?

Apply the vendor's patch.

## Is CVE-2025-23359 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-23359 exists.

## Other vulnerabilities in NVIDIA Container Toolkit

- [CVE-2024-0132](https://insights.sbomify.com/CVE-2024-0132/): NVIDIA Container Toolkit contains a Time-of-check Time-of-Use (TOCTOU) vulnerability (critical 9.0)
- [CVE-2024-0135](https://insights.sbomify.com/CVE-2024-0135/): Privilege escalation in NVIDIA Container Toolkit (high 7.6)
- [CVE-2024-0136](https://insights.sbomify.com/CVE-2024-0136/): Privilege escalation in NVIDIA Container Toolkit (high 7.6)
- [CVE-2024-0137](https://insights.sbomify.com/CVE-2024-0137/): Privilege escalation in NVIDIA Container Toolkit (medium 5.5)
- [CVE-2024-0134](https://insights.sbomify.com/CVE-2024-0134/): Path traversal in NVIDIA Container Toolkit (medium 4.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-23359 and fix it if it is affected.

What it is: CVE-2025-23359 is a high-severity vulnerability in NVIDIA Container Toolkit, published on 12 Feb 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-23359 exists.

Affected product: NVIDIA Container Toolkit. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-23359/ (Markdown: https://insights.sbomify.com/CVE-2025-23359/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-23359
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-23359
- OSV: https://osv.dev/vulnerability/CVE-2025-23359

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-23359/
Summaries are generated and may contain mistakes; the official description above is the record.
