CVSS 3.1
9.0 criticalCVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:HKnown 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.
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:Hgithub.com/NVIDIA/nvidia-container-toolkit (Go): fixed in 1.17.8github.com/NVIDIA/k8s-device-plugin (Go): fixed in 0.17.3github.com/NVIDIA/gpu-operator (Go): fixed in 25.3.2github.com/NVIDIA/mig-parted (Go): fixed in 0.12.2Explain 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.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| NVIDIA Container Toolkit | NVIDIA Container Toolkit All versions up to and including 1.17.7 |
| NVIDIA Container Toolkit | NVIDIA GPU Operator All versions up to and including 25.3.0 (CDI |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-vmg3-7v43-9g23 | Go | github.com/NVIDIA/nvidia-container-toolkit | <1.17.8 | 1.17.8 |
| GHSA-vmg3-7v43-9g23 | Go | github.com/NVIDIA/k8s-device-plugin | <0.17.3 | 0.17.3 |
| GHSA-vmg3-7v43-9g23 | Go | github.com/NVIDIA/gpu-operator | <25.3.2 | 25.3.2 |
| GHSA-vmg3-7v43-9g23 | Go | github.com/NVIDIA/mig-parted | <0.12.2 | 0.12.2 |
| GO-2025-3992 | Go | github.com/NVIDIA/gpu-operator | all versions | no fix published |
| GO-2025-3992 | Go | github.com/NVIDIA/k8s-device-plugin | <0.17.3 | 0.17.3 |
| GO-2025-3992 | Go | github.com/NVIDIA/mig-parted | <0.12.2 | 0.12.2 |
| GO-2025-3992 | Go | github.com/NVIDIA/nvidia-container-toolkit | <1.17.8 | 1.17.8 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Red Hat | enterprise_linux:9::appstream | toolbox, toolbox-tests, toolbox-debuginfo and 1 more | 0:0.2-1.el9_6 | RHSA-2025:13673 |
| Red Hat | enterprise_linux:10.0 | toolbox, toolbox-tests, toolbox-debuginfo and 1 more | 0:0.2-1.el10_0 | RHSA-2025:13674 |
| SUSE | Enterprise Storage 7.1, Linux Enterprise High Performance Computing 15 SP3-LTSS, Linux Enterprise High Performance Computing 15 SP4-ESPOS and 11 more | nvidia-container-toolkit | 1.18.0-150200.5.17.1 | SUSE-SU-2025:4187-1 |
| SUSE | Linux Enterprise Module for Package Hub 15 SP6 | govulncheck-vulndb | 0.0.20251023T162509-150000.1.110.1 | SUSE-SU-2025:3799-1 |
| openSUSE | Leap 15.6 | govulncheck-vulndb | 0.0.20251023T162509-150000.1.110.1 | SUSE-SU-2025:3799-1 |
| openSUSE | Leap 15.6 | nvidia-container-toolkit | 1.18.0-150200.5.17.1 | SUSE-SU-2025:4187-1 |
| openSUSE | Leap 16.0 | govulncheck-vulndb | 0.0.20260723T184607-160000.1.1 | openSUSE-SU-2026:21483-1 |
| openSUSE | Tumbleweed | govulncheck-vulndb | 0.0.20251023T162509-1.1 | openSUSE-SU-2025:15666-1 |
| AlmaLinux | 9 | toolbox, toolbox-tests | 0.2-1.el9_6 | ALSA-2025:13673 |
| AlmaLinux | 10 | toolbox, toolbox-tests | 0.2-1.el10_0 | ALSA-2025:13674 |
| Azure Linux | 2 | nvidia-container-toolkit | 1.17.8-1 | AZL-65651 |
| Azure Linux | 3 | nvidia-container-toolkit | 1.17.8-1 | AZL-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 rates this Important.
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.
No mitigation is currently available that meets Red Hat Product Security’s standards for usability, deployment, applicability, or stability.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | toolbox-0:0.2-1.el10_0 | Fixed 2025-08-12 | RHSA-2025:13674 |
| Red Hat Enterprise Linux 9 | toolbox-0:0.2-1.el9_6 | Fixed 2025-08-12 | RHSA-2025:13673 |
| Red Hat Enterprise Linux AI (RHEL AI) | rhelai1/bootc-amd-rhel9 | Not affected | |
| Red Hat Enterprise Linux AI (RHEL AI) | rhelai1/bootc-aws-nvidia-rhel9 | Not affected | |
| Red Hat Enterprise Linux AI (RHEL AI) | rhelai1/bootc-azure-amd-rhel9 | Not affected | |
| Red Hat Enterprise Linux AI (RHEL AI) | rhelai1/bootc-azure-nvidia-rhel9 | Not affected | |
| Red Hat Enterprise Linux AI (RHEL AI) | rhelai1/bootc-gcp-nvidia-rhel9 | Not affected | |
| Red Hat Enterprise Linux AI (RHEL AI) | rhelai1/bootc-intel-rhel9 | Not affected | |
| Red Hat Enterprise Linux AI (RHEL AI) | rhelai1/bootc-nvidia-rhel9 | Not affected | |
| Red Hat Enterprise Linux AI (RHEL AI) | rhelai1/granite-3.1-8b-lab-v2.1 | Not affected | |
| Red Hat Enterprise Linux AI (RHEL AI) | rhelai1/granite-3.1-8b-starter-v2.1 | Not affected | |
| Red Hat Enterprise Linux AI (RHEL AI) | rhelai1/instructlab-amd-rhel9 | Not affected | |
| Red Hat Enterprise Linux AI (RHEL AI) | rhelai1/instructlab-nvidia-rhel9 | Not affected | |
| Red Hat Enterprise Linux AI (RHEL AI) | rhelai1/modelcar-granite-3-1-8b-lab-v2-1 | Not affected | |
| Red Hat Enterprise Linux AI (RHEL AI) | rhelai1/modelcar-granite-3-1-8b-starter-v2-1 | Not affected | |
| Red Hat OpenShift Container Platform 4 | openshift/ose-rhel-coreos-8 | Not affected | |
| Red Hat OpenShift Container Platform 4 | openshift/ose-rhel-coreos-9 | Not affected | |
| Red Hat OpenShift Container Platform 4 | toolbox | Not 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.
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.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.