Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2025-23359

NVIDIA Container Toolkit for Linux contains a Time-of-Check Time-of-Use (TOCTOU) vulnerability when used with default configuration, where…

High8.3EPSS 3.7%
Published
Updated
Reserved
Assigned by
nvidia

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.

Scores

CVSS scores of CVE-2025-23359, by who scored it
Scored byCVSSScoreVector
nvidiaCNA (assigner)3.1High8.3CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
NVDNVD · Analyzed3.1High8.1CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
3.7% · top 10% of all CVEs (6 Nov 2026)
CISA SSVC
Exploitation: poc · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.3.

Weakness

Affected products

What to do

Workaround: This vulnerability does not impact use cases where CDI is used. The fix for this vulnerability changes the default behavior of the NVIDIA Container Toolkit. By default the NVIDIA CUDA compatibility libraries from /usr/local/cuda/compat in the container are no longer mounted to the default library path in the container being run. This may affect certain applications that depend on this behavior. A feature flag, allow-cuda-compat-libs-from-container was included in the NVIDIA Container Toolkit to allow users to opt-in to the previous behavior if required. Warning: Opting-in to the previous behavior will remove protection against this vulnerability and is not recommended. To set the feature flag ensure that the NVIDIA Container Toolkit config file at /etc/nvidia-container-runtime/config.toml includes: [features]   allow-cuda-compat-libs-from-container = true  Setting the value above to false or removing the config file entry will disable the feature. In the case of the NVIDIA GPU Operator the feature flag can be set by including the following in the NVIDIA GPU Operator helm install command: --set "toolkit.env[0].name=NVIDIA_CONTAINER_TOOLKIT_OPT_IN_FEATURES" --set "toolkit.env[0].value=allow-cuda-compat-libs-from-container"   For users who know that their application needs CUDA Forward Compatibility the following workaround can be used: Setting the LD_LIBRARY_PATH environment variable to include /usr/local/cuda/compat This may cause portability issues for some containers when running across multiple driver versions – especially when these are more recent than the compatibility libraries in the container.

References (2)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-23359 badge
[![CVE-2025-23359](https://trackcve.app/badge/CVE-2025-23359.svg)](https://trackcve.app/cve/CVE-2025-23359)

Record last updated .