cve.bz

CVE-2025-23266 (NVIDIAScape) nvidia container toolkit: Untrusted Search Path

9.0 criticalEPSS 3.0%Fix available

Known as NVIDIAScape

Critical (9.0) in nvidia container toolkit. EPSS 3.0% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/NVIDIA/nvidia-container-toolkit 1.17.8.

On this page
NVIDIA Container Toolkit for all platforms contains a vulnerability in some hooks used to initialize the container, where an attacker could execute arbitrary code with elevated permissions. A successful exploit of this vulnerability might lead to escalation of privileges, data tampering, information disclosure, and denial of service.

Severity

CVSS 3.1

9.0 critical
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS
3.0% (down from 3.3% a week ago; 3.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 88th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2025-07-18. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-426 Untrusted Search Path
OWASP Top 10
A08:2025 Software or Data Integrity Failures
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • github.com/NVIDIA/nvidia-container-toolkit (Go): fixed in 1.17.8
  • github.com/NVIDIA/k8s-device-plugin (Go): fixed in 0.17.3
  • github.com/NVIDIA/gpu-operator (Go): fixed in 25.3.2
  • github.com/NVIDIA/mig-parted (Go): fixed in 0.12.2
  • Red Hat, SUSE, openSUSE, AlmaLinux, Azure Linux: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2025-23266 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-23266?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-23266?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-23266 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
NVIDIA Container ToolkitNVIDIA Container Toolkit All versions up to and including 1.17.7
NVIDIA Container ToolkitNVIDIA GPU Operator All versions up to and including 25.3.0 (CDI

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-vmg3-7v43-9g23Gogithub.com/NVIDIA/nvidia-container-toolkit<1.17.81.17.8
GHSA-vmg3-7v43-9g23Gogithub.com/NVIDIA/k8s-device-plugin<0.17.30.17.3
GHSA-vmg3-7v43-9g23Gogithub.com/NVIDIA/gpu-operator<25.3.225.3.2
GHSA-vmg3-7v43-9g23Gogithub.com/NVIDIA/mig-parted<0.12.20.12.2
GO-2025-3992Gogithub.com/NVIDIA/gpu-operatorall versionsno fix published
GO-2025-3992Gogithub.com/NVIDIA/k8s-device-plugin<0.17.30.17.3
GO-2025-3992Gogithub.com/NVIDIA/mig-parted<0.12.20.12.2
GO-2025-3992Gogithub.com/NVIDIA/nvidia-container-toolkit<1.17.81.17.8

Linux distributions

DistributionReleasePackageFixed inAdvisory
Red Hatenterprise_linux:9::appstreamtoolbox, toolbox-tests, toolbox-debuginfo and 1 more0:0.2-1.el9_6RHSA-2025:13673
Red Hatenterprise_linux:10.0toolbox, toolbox-tests, toolbox-debuginfo and 1 more0:0.2-1.el10_0RHSA-2025:13674
SUSEEnterprise Storage 7.1, Linux Enterprise High Performance Computing 15 SP3-LTSS, Linux Enterprise High Performance Computing 15 SP4-ESPOS and 11 morenvidia-container-toolkit1.18.0-150200.5.17.1SUSE-SU-2025:4187-1
SUSELinux Enterprise Module for Package Hub 15 SP6govulncheck-vulndb0.0.20251023T162509-150000.1.110.1SUSE-SU-2025:3799-1
openSUSELeap 15.6govulncheck-vulndb0.0.20251023T162509-150000.1.110.1SUSE-SU-2025:3799-1
openSUSELeap 15.6nvidia-container-toolkit1.18.0-150200.5.17.1SUSE-SU-2025:4187-1
openSUSELeap 16.0govulncheck-vulndb0.0.20260723T184607-160000.1.1openSUSE-SU-2026:21483-1
openSUSETumbleweedgovulncheck-vulndb0.0.20251023T162509-1.1openSUSE-SU-2025:15666-1
AlmaLinux9toolbox, toolbox-tests0.2-1.el9_6ALSA-2025:13673
AlmaLinux10toolbox, toolbox-tests0.2-1.el10_0ALSA-2025:13674
Azure Linux2nvidia-container-toolkit1.17.8-1AZL-65651
Azure Linux3nvidia-container-toolkit1.17.8-1AZL-65648

From the distributions' data via OSV.dev: Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0; AlmaLinux's OSV database, MIT; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Red Hat · SUSE · openSUSE.

Red Hat

Red Hat rates this Important.

Red Hat's statement

RHEL AI is not affected because it uses CDI mode with NVIDIA Container Toolkit versions later than 1.17.5, which are not vulnerable, and does not rely on the enable-cuda-compat hook, thereby eliminating the attack vector entirely.

This vulnerability is marked as Important rather than Critical primarily due to its attack prerequisites and execution context, despite its high CVSS score. While the vulnerability allows privilege escalation via the enable-cuda-compat hook in the NVIDIA Container Toolkit, it is not exploitable remotely—it requires local access and low privileges within a containerized environment. This significantly reduces its initial attack surface compared to a truly critical vulnerability that could be exploited over the network without authentication.

Red Hat's mitigation

No mitigation is currently available that meets Red Hat Product Security’s standards for usability, deployment, applicability, or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10toolbox-0:0.2-1.el10_0Fixed 2025-08-12RHSA-2025:13674
Red Hat Enterprise Linux 9toolbox-0:0.2-1.el9_6Fixed 2025-08-12RHSA-2025:13673
Red Hat Enterprise Linux AI (RHEL AI)rhelai1/bootc-amd-rhel9Not affected
Red Hat Enterprise Linux AI (RHEL AI)rhelai1/bootc-aws-nvidia-rhel9Not affected
Red Hat Enterprise Linux AI (RHEL AI)rhelai1/bootc-azure-amd-rhel9Not affected
Red Hat Enterprise Linux AI (RHEL AI)rhelai1/bootc-azure-nvidia-rhel9Not affected
Red Hat Enterprise Linux AI (RHEL AI)rhelai1/bootc-gcp-nvidia-rhel9Not affected
Red Hat Enterprise Linux AI (RHEL AI)rhelai1/bootc-intel-rhel9Not affected
Red Hat Enterprise Linux AI (RHEL AI)rhelai1/bootc-nvidia-rhel9Not affected
Red Hat Enterprise Linux AI (RHEL AI)rhelai1/granite-3.1-8b-lab-v2.1Not affected
Red Hat Enterprise Linux AI (RHEL AI)rhelai1/granite-3.1-8b-starter-v2.1Not affected
Red Hat Enterprise Linux AI (RHEL AI)rhelai1/instructlab-amd-rhel9Not affected
Red Hat Enterprise Linux AI (RHEL AI)rhelai1/instructlab-nvidia-rhel9Not affected
Red Hat Enterprise Linux AI (RHEL AI)rhelai1/modelcar-granite-3-1-8b-lab-v2-1Not affected
Red Hat Enterprise Linux AI (RHEL AI)rhelai1/modelcar-granite-3-1-8b-starter-v2-1Not affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Not affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9Not affected
Red Hat OpenShift Container Platform 4toolboxNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2025-23266.

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

Attack patterns (CAPEC)

  • CAPEC-38 Leveraging/Manipulating Configuration File Search Paths Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON