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.

Update within 1.17:go get github.com/NVIDIA/nvidia-container-toolkit@v1.17.9

Is your project on an affected github.com/NVIDIA/nvidia-container-toolkit?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

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

  • LowCVE-2025-23266GO-2025-399223 Oct 2025

    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
  • LowCVE-2025-23267GO-2025-399823 Oct 2025

    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
  • CriticalCVE-2025-23266GHSA-vmg3-7v43-9g2317 Jul 2025

    NVIDIA Container Toolkit for all platforms contains an Untrusted Search Path

    Affected
    <1.17.8
    Fixed in
    1.17.8
  • HighCVE-2025-23267GHSA-67jc-hmvg-q4c717 Jul 2025

    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.

VersionKnown advisories
github.com/NVIDIA/nvidia-container-toolkit 1.17.9None
github.com/NVIDIA/nvidia-container-toolkit 1.17.8None
github.com/NVIDIA/nvidia-container-toolkit 1.17.7CVE-2025-23266, CVE-2025-23267, CVE-2025-23266, CVE-2025-23267
github.com/NVIDIA/nvidia-container-toolkit 1.17.6CVE-2025-23266, CVE-2025-23267, CVE-2025-23266, CVE-2025-23267
github.com/NVIDIA/nvidia-container-toolkit 1.17.5CVE-2025-23266, CVE-2025-23267, CVE-2025-23266, CVE-2025-23267
github.com/NVIDIA/nvidia-container-toolkit 1.17.4CVE-2025-23266, CVE-2025-23267, CVE-2025-23266, CVE-2025-23267
github.com/NVIDIA/nvidia-container-toolkit 1.17.3CVE-2025-23266, CVE-2025-23267, CVE-2025-23266, CVE-2025-23267
github.com/NVIDIA/nvidia-container-toolkit 1.17.2CVE-2025-23266, CVE-2025-23267, CVE-2025-23266, CVE-2025-23267
github.com/NVIDIA/nvidia-container-toolkit 1.17.1CVE-2025-23266, CVE-2025-23267, CVE-2025-23266, CVE-2025-23267
github.com/NVIDIA/nvidia-container-toolkit 1.17.0CVE-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

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.