Is github.com/NVIDIA/nvidia-container-toolkit 1.17 vulnerable?
Go · 10 releases from 1.17.0 to 1.17.9 · latest github.com/NVIDIA/nvidia-container-toolkit is 1.20.2 · checked 18 Nov 2026
No known advisories in the last release
github.com/NVIDIA/nvidia-container-toolkit 1.17.9, the last 1.17 release, has no known advisories. 4 advisories affect earlier 1.17.x releases, so update to 1.17.9.
go get github.com/NVIDIA/nvidia-container-toolkit@v1.17.9Is your project on an affected github.com/NVIDIA/nvidia-container-toolkit?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Fixed within 1.17.x, affecting earlier releases
NVIDIA Container Toolkit for all platforms contains an Untrusted Search Path in github.com/NVIDIA/gpu-operator
- Affected
- <1.17.8
- Fixed in
- 1.17.8
NVIDIA Container Toolkit for all platforms contains a vulnerability in the update-ldcache hook in github.com/NVIDIA/gpu-operator
- Affected
- <1.17.8
- Fixed in
- 1.17.8
NVIDIA Container Toolkit for all platforms contains an Untrusted Search Path
- Affected
- <1.17.8
- Fixed in
- 1.17.8
NVIDIA Container Toolkit for all platforms contains a vulnerability in the update-ldcache hook
- Affected
- <1.17.8
- Fixed in
- 1.17.8
Every github.com/NVIDIA/nvidia-container-toolkit 1.17.x release
Affected: 1.17.0 to 1.17.7. 1.17.8 and later are not affected. Latest github.com/NVIDIA/nvidia-container-toolkit: 1.20.2.
| Version | Known advisories |
|---|---|
| github.com/NVIDIA/nvidia-container-toolkit 1.17.9 | None |
| github.com/NVIDIA/nvidia-container-toolkit 1.17.8 | None |
| github.com/NVIDIA/nvidia-container-toolkit 1.17.7 | CVE-2025-23266, CVE-2025-23267, CVE-2025-23266, CVE-2025-23267 |
| github.com/NVIDIA/nvidia-container-toolkit 1.17.6 | CVE-2025-23266, CVE-2025-23267, CVE-2025-23266, CVE-2025-23267 |
| github.com/NVIDIA/nvidia-container-toolkit 1.17.5 | CVE-2025-23266, CVE-2025-23267, CVE-2025-23266, CVE-2025-23267 |
| github.com/NVIDIA/nvidia-container-toolkit 1.17.4 | CVE-2025-23266, CVE-2025-23267, CVE-2025-23266, CVE-2025-23267 |
| github.com/NVIDIA/nvidia-container-toolkit 1.17.3 | CVE-2025-23266, CVE-2025-23267, CVE-2025-23266, CVE-2025-23267 |
| github.com/NVIDIA/nvidia-container-toolkit 1.17.2 | CVE-2025-23266, CVE-2025-23267, CVE-2025-23266, CVE-2025-23267 |
| github.com/NVIDIA/nvidia-container-toolkit 1.17.1 | CVE-2025-23266, CVE-2025-23267, CVE-2025-23266, CVE-2025-23267 |
| github.com/NVIDIA/nvidia-container-toolkit 1.17.0 | CVE-2025-23266, CVE-2025-23267, CVE-2025-23266, CVE-2025-23267 |
Which of your client projects are still on github.com/NVIDIA/nvidia-container-toolkit 1.17?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact github.com/NVIDIA/nvidia-container-toolkit version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other github.com/NVIDIA/nvidia-container-toolkit versions
- github.com/NVIDIA/nvidia-container-toolkit 1.20
- github.com/NVIDIA/nvidia-container-toolkit 1.19
- github.com/NVIDIA/nvidia-container-toolkit 1.18
- github.com/NVIDIA/nvidia-container-toolkit 1.16
- github.com/NVIDIA/nvidia-container-toolkit 1.15
- github.com/NVIDIA/nvidia-container-toolkit 1.14
- All github.com/NVIDIA/nvidia-container-toolkit advisories
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Go registry. Refreshed daily.