VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/NVIDIA/nvidia-container-toolkit: vulnerability history, versions and safety

github.com/NVIDIA/nvidia-container-toolkit is a package in the Go ecosystem. Vulert records 8 vulnerabilities for it across 120 releases, from Sep 2024 to Jul 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
8 vulnerabilities recorded C3 H1 M2 U2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all github.com/NVIDIA/nvidia-container-toolkit vulnerabilities

Vulert verdict on github.com/NVIDIA/nvidia-container-toolkit v1.20.1 i

Updated on 23 Oct 2026

Action needed: v1.20.1 has 8 known vulnerabilities, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 80/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release v1.20.1 — affected i
  • Vulnerabilities on record 8 over 1 year · 0 in the last year i
  • Latest disclosure 17 Jul 2025 i
  • Highest CVSS 9.0 i
  • With no published fix 0 i
  • Stars 4,599 i
  • OpenSSF scorecard 4/10 i
  • Last release 1 month ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by the Go module proxy, refreshed 22 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for github.com/NVIDIA/nvidia-container-toolkit, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
v0.0.0-20261019221757-44f1c6ef98c9 19 Oct 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.1-0.20261019221757-44f1c6ef98c9 19 Oct 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v0.0.0-20261014231746-3e112b4af299 14 Oct 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.1-0.20261014231746-3e112b4af299 14 Oct 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.1-0.20261014191940-97629469e563 14 Oct 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v0.0.0-20261013222321-cec3a629d1ae 13 Oct 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.1-0.20261013222321-cec3a629d1ae 13 Oct 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v0.0.0-20261012174206-023f35906ee2 12 Oct 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.1-0.20261012174206-023f35906ee2 12 Oct 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.1-0.20261008212934-e9fd70f19d51 08 Oct 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.2-0.20261004081250-81b7388e1ab3 04 Oct 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v0.0.0-20261001225500-a672e378ef91 01 Oct 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.1-0.20261001225500-a672e378ef91 01 Oct 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.1-0.20261001195644-c06d8ee0a5c6 01 Oct 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.1-0.20261001155933-f460f7d1c499 01 Oct 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.1-0.20261001084711-8884e35d0f5c 01 Oct 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.1-0.20260928191646-1baab56dd679 28 Sep 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.1-0.20260928191431-0aabe0b01db9 28 Sep 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v0.0.0-20260921212441-84e2c2c182bf 21 Sep 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.1-0.20260921212441-84e2c2c182bf 21 Sep 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.1-0.20260920031226-f2e1bdf879db 20 Sep 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.1 16 Sep 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.1-0.20260916203248-8bc9a7ea12ee 16 Sep 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.1-0.20260916175536-99d1efb99e20 16 Sep 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v0.0.0-20260916175518-3a6c050d9c0c 16 Sep 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.1-0.20260916175518-3a6c050d9c0c 16 Sep 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.1-0.20260916171312-1e5fb484c9f1 16 Sep 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v0.0.0-20260915181408-9bc67087e3de 15 Sep 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.1-0.20260915181408-9bc67087e3de 15 Sep 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.1-0.20260915174045-3b82063d410e 15 Sep 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.1-0.20260915081245-6a44f7732d69 15 Sep 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.1-0.20260914195404-24761af0847d 14 Sep 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v0.0.0-20260914192833-3c435c9048e1 14 Sep 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.1-0.20260914192833-3c435c9048e1 14 Sep 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.1-0.20260913225516-544986ee296a 13 Sep 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.1-0.20260913220301-9ed3ff44ad0f 13 Sep 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.1-0.20260913025521-6e8b4d18e8cf 13 Sep 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.1-0.20260913023842-6f3e7dc47d31 13 Sep 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v0.0.0-20260912233826-b4df771174da 12 Sep 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.1-0.20260912233826-b4df771174da 12 Sep 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.1-0.20260912051019-bd0ff886d762 12 Sep 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.1-0.20260911224648-9e09f790b763 11 Sep 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v0.0.0-20260911155705-341598c1c36a 11 Sep 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.1-0.20260911155705-341598c1c36a 11 Sep 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.1-0.20260911034009-fcca9a9c8c6b 11 Sep 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v0.0.0-20260909001433-4165c0ebdbbf 09 Sep 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.1-0.20260909001433-4165c0ebdbbf 09 Sep 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v0.0.0-20260904223653-752e1e571bdf 04 Sep 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.1-0.20260904223653-752e1e571bdf 04 Sep 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.1-0.20260903215835-a471da0e7eba 03 Sep 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v0.0.0-20260902200748-43e82358547c 02 Sep 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.1-0.20260902200748-43e82358547c 02 Sep 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v0.0.0-20260828220121-3121efcf04bf 28 Aug 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.1-0.20260828220121-3121efcf04bf 28 Aug 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.1-0.20260828175627-5bd3282fb824 28 Aug 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.1-0.20260827230319-1d87654d507a 27 Aug 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v0.0.0-20260825160319-b5a4721daa18 25 Aug 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.1-0.20260825160319-b5a4721daa18 25 Aug 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.1-0.20260821231732-d34b3046758c 21 Aug 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v0.0.0-20260821180335-1780ac699db7 21 Aug 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.1-0.20260821180335-1780ac699db7 21 Aug 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.1-0.20260819195341-357b97081426 19 Aug 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v0.0.0-20260818162332-26f29323af46 18 Aug 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.1-0.20260818162332-26f29323af46 18 Aug 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v0.0.0-20260817201339-5eee4c5f30d8 17 Aug 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.1-0.20260817201339-5eee4c5f30d8 17 Aug 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v0.0.0-20260814164112-cb5d6990b806 14 Aug 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.1-0.20260814081824-f3d5f234f4e6 14 Aug 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v0.0.0-20260814003030-ef54448e413e 14 Aug 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.1-0.20260814003030-ef54448e413e 14 Aug 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.0 12 Aug 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v0.0.0-20260812010449-2d268189d81b 12 Aug 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.0-rc.1.0.20260812010449-2d268189d81b 12 Aug 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v0.0.0-20260807162041-a99639011780 07 Aug 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.0-rc.1.0.20260807162041-a99639011780 07 Aug 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v0.0.0-20260804205613-f86148376a4f 04 Aug 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.0-rc.1.0.20260804205613-f86148376a4f 04 Aug 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v0.0.0-20260731162813-828fc6ce327d 31 Jul 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.0-rc.1.0.20260731162813-828fc6ce327d 31 Jul 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v0.0.0-20260730230540-4b1922e5757c 30 Jul 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.0-rc.1.0.20260730230540-4b1922e5757c 30 Jul 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v0.0.0-20260730190939-3ad3bb6a5b90 30 Jul 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.0-rc.1.0.20260730190939-3ad3bb6a5b90 30 Jul 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v0.0.0-20260727174247-1151f0130747 27 Jul 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.0-rc.1.0.20260727174247-1151f0130747 27 Jul 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v0.0.0-20260723213629-f7cb44c51c35 23 Jul 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.0-rc.1.0.20260723213629-f7cb44c51c35 23 Jul 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v0.0.0-20260717185509-1cddfb0dc179 17 Jul 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.0-rc.1.0.20260717185509-1cddfb0dc179 17 Jul 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v0.0.0-20260710195145-3db41dec03bf 10 Jul 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.0-rc.1.0.20260710195145-3db41dec03bf 10 Jul 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.0-rc.1.0.20260710055937-312b675b7c06 10 Jul 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v0.0.0-20260708222945-803579e78923 08 Jul 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.20.0-rc.1 08 Jul 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v0.0.0-20260706195448-8807d7c76360 06 Jul 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.19.1-0.20260706195448-8807d7c76360 06 Jul 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v0.0.0-20260702201721-69c285d7fd8f 02 Jul 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.19.1-0.20260702201721-69c285d7fd8f 02 Jul 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v0.0.0-20260630174012-05e941dffa81 30 Jun 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v1.19.1-0.20260630174012-05e941dffa81 30 Jun 2026 C3 H1 M2 U2 Apache-2.0 Yes Details →
v0.0.0-20260625200300-41dd4444a23f 25 Jun 2026 C3 H1 M2 U2 — Yes Details →
v1.19.1-0.20260625200300-41dd4444a23f 25 Jun 2026 C3 H1 M2 U2 — Yes Details →
v0.0.0-20260623213634-6fe425a59d0f 23 Jun 2026 C3 H1 M2 U2 — Yes Details →
v1.19.1-0.20260623213634-6fe425a59d0f 23 Jun 2026 C3 H1 M2 U2 — Yes Details →
v0.0.0-20260616153722-6d1a53dbd83f 16 Jun 2026 C3 H1 M2 U2 — Yes Details →
v1.19.1-0.20260616153722-6d1a53dbd83f 16 Jun 2026 C3 H1 M2 U2 — Yes Details →
v0.0.0-20260616023624-af0aaa4575cb 16 Jun 2026 C3 H1 M2 U2 — Yes Details →
v1.19.1-0.20260616023624-af0aaa4575cb 16 Jun 2026 C3 H1 M2 U2 — Yes Details →
v0.0.0-20260616010451-bcca48d46150 16 Jun 2026 C3 H1 M2 U2 — Yes Details →
v1.19.1-0.20260616010451-bcca48d46150 16 Jun 2026 C3 H1 M2 U2 — Yes Details →
v0.0.0-20260611164142-59c042086ec2 11 Jun 2026 C3 H1 M2 U2 — Yes Details →
v1.19.1-0.20260611164142-59c042086ec2 11 Jun 2026 C3 H1 M2 U2 — Yes Details →
v0.0.0-20260609002849-538606ca9f49 09 Jun 2026 C3 H1 M2 U2 — Yes Details →
v1.19.1-0.20260609002849-538606ca9f49 09 Jun 2026 C3 H1 M2 U2 — Yes Details →
v1.19.2-0.20260609002610-0e6591fde5c1 09 Jun 2026 C3 H1 M2 U2 — Yes Details →
v0.0.0-20260605192254-e0bcfd493755 05 Jun 2026 C3 H1 M2 U2 — Yes Details →
v1.19.1-0.20260605192254-e0bcfd493755 05 Jun 2026 C3 H1 M2 U2 — Yes Details →
v1.19.1-0.20260605062543-a8f29f3e839c 05 Jun 2026 C3 H1 M2 U2 — Yes Details →
v0.0.0-20260604165447-1f7480c8c9f6 04 Jun 2026 C3 H1 M2 U2 — Yes Details →
v1.19.1-0.20260604165447-1f7480c8c9f6 04 Jun 2026 C3 H1 M2 U2 — Yes Details →

The newest 120 of 554 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 6
  • 2025 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 8 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for github.com/NVIDIA/nvidia-container-toolkit

The 5 most severe of 8 vulnerabilities recorded for this package

Search all 8 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical TOCTOU Vulnerability in NVIDIA Container Toolkit 9.0 critical 1.16.2 26 Sep 2024
CVE-2024-0132: NVIDIA Container Toolkit TOCTOU Vulnerability Leading to Host File System Access 9.0 critical 1.16.2 29 Oct 2024
CVE-2025-23266: NVIDIA Container Toolkit Untrusted Search Path Vulnerability 9.0 critical 1.17.8 17 Jul 2025
CVE-2025-23267: NVIDIA Container Toolkit Vulnerability in update-ldcache Hook Leading to Data Tampering 8.5 high 1.17.8 17 Jul 2025
CVE-2024-0133: NVIDIA Container Toolkit Allows Host File System Manipulation via Malicious Container Images 4.1 medium 1.16.2 29 Oct 2024

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About github.com/NVIDIA/nvidia-container-toolkit

Is github.com/NVIDIA/nvidia-container-toolkit safe to use?

Vulert records 8 vulnerabilities for github.com/NVIDIA/nvidia-container-toolkit in Go: 3 critical, 1 high, 2 medium and 0 low, plus 2 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is github.com/NVIDIA/nvidia-container-toolkit's Vulert package health score?

Vulert scores github.com/NVIDIA/nvidia-container-toolkit 80/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of github.com/NVIDIA/nvidia-container-toolkit affected?

Yes. v1.20.1, the version you would install today, has 8 known vulnerabilities, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of github.com/NVIDIA/nvidia-container-toolkit should I use?

v1.20.1 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does github.com/NVIDIA/nvidia-container-toolkit have?

8 vulnerabilities are recorded for github.com/NVIDIA/nvidia-container-toolkit in the Go ecosystem: 3 critical, 1 high, 2 medium and 0 low, plus 2 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new github.com/NVIDIA/nvidia-container-toolkit vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/NVIDIA/nvidia-container-toolkit in the last 12 months, and the oldest entry in this database dates to 26 Sep 2024. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of github.com/NVIDIA/nvidia-container-toolkit are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor github.com/NVIDIA/nvidia-container-toolkit for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/NVIDIA/nvidia-container-toolkit version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.