VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

nemo-toolkit: vulnerability history, versions and safety

nemo-toolkit is a package in the PyPI ecosystem. Vulert records 11 vulnerabilities for it across 103 releases, from Jan 2022 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
11 vulnerabilities recorded H4 M1 L1 U5
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
9 in the last 12 months

Most recent disclosure 13 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all nemo-toolkit vulnerabilities

Vulert verdict on nemo-toolkit 3.0.0 i

Updated on 23 Oct 2026

Good news: 3.0.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 11.

Package health score 69/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Active

What to do: Stay on 3.0.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 3.0.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 3.0.0 — unaffected i
  • Vulnerabilities on record 11 over 4 years · 9 in the last year i
  • Latest disclosure 13 Jul 2026 i
  • Highest CVSS 8.0 i
  • With no published fix 0 i
  • Depended on by 50 packages i
  • Stars 18,603 i
  • Last release 2 months ago i
  • Licence non-standard i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 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 nemo-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
3.0.0 07 Aug 2026 none non-standard — Details →
2.7.3 23 Apr 2026 none non-standard — Details →
2.7.2 25 Mar 2026 none non-standard — Details →
2.7.1 20 Mar 2026 none non-standard — Details →
2.7.0 26 Feb 2026 none non-standard — Details →
2.6.2 06 Feb 2026 none non-standard — Details →
2.6.1 09 Jan 2026 H2 U2 non-standard Yes Details →
2.6.0 03 Dec 2025 H4 U4 non-standard Yes Details →
2.6.0rc0 03 Dec 2025 H4 U4 non-standard Yes Details →
2.5.3 10 Nov 2025 H4 U4 non-standard Yes Details →
2.5.2 27 Oct 2025 H4 U4 non-standard Yes Details →
2.5.1 22 Oct 2025 H4 U4 non-standard Yes Details →
2.5.0 07 Oct 2025 H4 U4 non-standard Yes Details →
2.4.1 30 Sep 2025 H4 U4 non-standard Yes Details →
2.3.3 25 Sep 2025 H4 U4 non-standard Yes Details →
2.5.0rc0 03 Aug 2025 H4 U4 non-standard Yes Details →
2.4.0 25 Jul 2025 H4 U4 non-standard Yes Details →
2.4.0rc2 09 Jul 2025 H4 U4 non-standard Yes Details →
2.3.2 08 Jul 2025 H4 U4 non-standard Yes Details →
2.4.0rc1 02 Jul 2025 H4 U4 non-standard Yes Details →
2.4.0rc0 27 Jun 2025 H4 U4 non-standard Yes Details →
2.3.1 25 May 2025 H4 U4 non-standard Yes Details →
2.3.0 08 May 2025 H4 U4 non-standard Yes Details →
2.3.0rc4 21 Apr 2025 H4 U4 non-standard Yes Details →
2.3.0rc3 15 Apr 2025 H4 U4 non-standard Yes Details →
2.3.0rc2 07 Apr 2025 H4 U4 non-standard Yes Details →
2.2.1 31 Mar 2025 H4 U4 non-standard Yes Details →
2.2.0 12 Mar 2025 H4 U4 non-standard Yes Details →
2.2.0rc3 25 Feb 2025 H4 U4 non-standard Yes Details →
2.2.0rc2 17 Feb 2025 H4 U4 non-standard Yes Details →
2.2.0rc1 04 Feb 2025 H4 U4 non-standard Yes Details →
2.2.0rc0 02 Feb 2025 H4 U4 non-standard Yes Details →
2.1.0 03 Jan 2025 H4 U4 non-standard Yes Details →
2.1.0rc2 21 Dec 2024 H4 U4 non-standard Yes Details →
2.1.0rc1 20 Dec 2024 H4 U4 non-standard Yes Details →
2.1.0rc0 11 Dec 2024 H4 U4 non-standard Yes Details →
2.0.0 14 Nov 2024 H4 U4 Apache-2.0 Yes Details →
2.0.0rc1 15 Aug 2024 H4 U4 Apache-2.0 Yes Details →
2.0.0rc0 06 Jun 2024 H4 U4 Apache-2.0 Yes Details →
1.23.0 28 Feb 2024 H4 U4 Apache-2.0 Yes Details →
1.22.0 10 Jan 2024 H4 U4 Apache-2.0 Yes Details →
1.21.0 25 Oct 2023 H4 U4 Apache-2.0 Yes Details →
1.20.0 04 Aug 2023 H4 U4 Apache-2.0 Yes Details →
1.19.1 13 Jul 2023 H4 U4 Apache-2.0 Yes Details →
1.19.0 15 Jun 2023 H4 U4 Apache-2.0 Yes Details →
1.18.1 17 May 2023 H4 U4 Apache-2.0 Yes Details →
1.18.0 12 May 2023 H4 U4 Apache-2.0 Yes Details →
1.17.0 04 Apr 2023 H4 U4 Apache-2.0 Yes Details →
1.16.0 08 Mar 2023 H4 U4 Apache-2.0 Yes Details →
1.15.0 01 Feb 2023 H4 U4 Apache-2.0 Yes Details →
1.14.0 24 Dec 2022 H4 U4 Apache-2.0 Yes Details →
1.13.0 07 Dec 2022 H4 U4 Apache-2.0 Yes Details →
1.12.0 10 Oct 2022 H4 U4 Apache-2.0 Yes Details →
1.11.0 08 Sep 2022 H4 U4 Apache-2.0 Yes Details →
1.10.0 01 Jul 2022 H4 U4 Apache-2.0 Yes Details →
1.9.0 03 Jun 2022 H4 U4 Apache-2.0 Yes Details →
1.8.2 26 Apr 2022 H4 U4 Apache-2.0 Yes Details →
1.8.1 22 Apr 2022 H4 U4 Apache-2.0 Yes Details →
1.8.0 20 Apr 2022 H4 U4 Apache-2.0 Yes Details →
1.7.2 17 Mar 2022 H4 U4 Apache-2.0 Yes Details →
1.7.1 08 Mar 2022 H4 U4 Apache-2.0 Yes Details →
1.7.0 01 Mar 2022 H4 U4 Apache-2.0 Yes Details →
1.6.2 05 Feb 2022 H4 U4 Apache-2.0 Yes Details →
1.6.1 02 Feb 2022 H4 U4 Apache-2.0 Yes Details →
1.6.0 29 Jan 2022 H4 U4 Apache-2.0 Yes Details →
1.5.1 04 Dec 2021 H4 M1 L1 U5 Apache-2.0 Yes Details →
1.5.0 19 Nov 2021 H4 M1 L1 U5 Apache-2.0 Yes Details →
1.4.0 02 Oct 2021 H4 M1 L1 U5 Apache-2.0 Yes Details →
1.3.0 27 Aug 2021 H4 M1 L1 U5 Apache-2.0 Yes Details →
1.2.0 30 Jul 2021 H4 M1 L1 U5 Apache-2.0 Yes Details →
1.1.0 02 Jul 2021 H4 M1 L1 U5 Apache-2.0 Yes Details →
1.0.2 11 Jun 2021 H4 M1 L1 U5 Apache-2.0 Yes Details →
1.0.1 09 Jun 2021 H4 M1 L1 U5 Apache-2.0 Yes Details →
1.0.0 03 Jun 2021 H4 M1 L1 U5 Apache-2.0 Yes Details →
1.0.0rc1 07 Apr 2021 H4 M1 L1 U5 Apache-2.0 Yes Details →
1.0.0b3 11 Dec 2020 H4 M1 L1 U5 Apache-2.0 Yes Details →
1.0.0b2 17 Nov 2020 H4 M1 L1 U5 Apache-2.0 Yes Details →
1.0.0b1 25 Sep 2020 H4 M1 L1 U5 Apache-2.0 Yes Details →
1.0.0b0 25 Sep 2020 H4 M1 L1 U5 Apache-2.0 Yes Details →
1.0.0a4 24 Sep 2020 H4 M1 L1 U5 Apache-2.0 Yes Details →
0.11.0 10 Jul 2020 H4 M1 L1 U5 Apache-2.0 Yes Details →
0.11.0b14 01 Jul 2020 H4 M1 L1 U5 Apache-2.0 Yes Details →
0.11.0b12 26 Jun 2020 H4 M1 L1 U5 Apache-2.0 Yes Details →
0.11.0b11 25 Jun 2020 H4 M1 L1 U5 Apache-2.0 Yes Details →
0.11.0b10 24 Jun 2020 H4 M1 L1 U5 Apache-2.0 Yes Details →
0.11.0b8 17 Jun 2020 H4 M1 L1 U5 Apache-2.0 Yes Details →
0.11.0b5 09 Jun 2020 H4 M1 L1 U5 Apache-2.0 Yes Details →
0.11.0b4 05 Jun 2020 H4 M1 L1 U5 Apache-2.0 Yes Details →
0.11.0b3 04 Jun 2020 H4 M1 L1 U5 Apache-2.0 Yes Details →
0.11.0b2 02 Jun 2020 H4 M1 L1 U5 Apache-2.0 Yes Details →
0.11.0b1 27 May 2020 H4 M1 L1 U5 Apache-2.0 Yes Details →
0.10.1 17 Apr 2020 H4 M1 L1 U5 Apache-2.0 Yes Details →
0.10.0 02 Apr 2020 H4 M1 L1 U5 Apache-2.0 Yes Details →
0.10.0b10 24 Mar 2020 H4 M1 L1 U5 Apache-2.0 Yes Details →
0.10.0b9 18 Mar 2020 H4 M1 L1 U5 Apache-2.0 Yes Details →
0.10.0b8 18 Mar 2020 H4 M1 L1 U5 Apache-2.0 Yes Details →
0.10.0b7 17 Mar 2020 H4 M1 L1 U5 Apache-2.0 Yes Details →
0.10.0b6 12 Mar 2020 H4 M1 L1 U5 Apache-2.0 Yes Details →
0.10.0b5 11 Mar 2020 H4 M1 L1 U5 Apache-2.0 Yes Details →
0.10.0b4 11 Mar 2020 H4 M1 L1 U5 Apache-2.0 Yes Details →
0.10.0b3 03 Mar 2020 H4 M1 L1 U5 — Yes Details →
0.10.0b2 02 Mar 2020 H4 M1 L1 U5 — Yes Details →
0.10.0b1 02 Mar 2020 H4 M1 L1 U5 — Yes Details →
0.10.0b0 25 Feb 2020 H4 M1 L1 U5 — Yes Details →
0.9.0 16 Dec 2019 H4 M1 L1 U5 — Yes Details →
0.8.2 15 Nov 2019 H4 M1 L1 U5 — Yes Details →
0.8.1 05 Nov 2019 H4 M1 L1 U5 — Yes Details →
0.8.0 19 Sep 2019 H4 M1 L1 U5 — Yes Details →
0.11.0b6.linux-x86_64 — H4 M1 L1 U5 — Yes Details →

All 109 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 2
  • 2026 9

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

03 Vulnerabilities

Recorded vulnerabilities for nemo-toolkit

The 5 most severe of 11 vulnerabilities recorded for this package

Search all 11 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-33245: Remote Code Execution Vulnerability in nemo-toolkit 8.0 high 2.6.1 18 Feb 2026
CVE-2025-33245: Remote Code Execution Vulnerability in nemo-toolkit 8.0 high 2.6.1 13 Jul 2026
CVE-2025-33253: Remote Code Execution Vulnerability in nemo-toolkit 7.8 high 2.6.1 18 Feb 2026
CVE-2026-24157: Remote Code Execution Vulnerability in NVIDIA NeMo Framework's Checkpoint Loading 7.8 high 2.6.2 24 Mar 2026
CVE-2026-24159: Remote Code Execution Vulnerability in NVIDIA NeMo Framework (nemo-toolkit) 7.8 high 2.6.2 24 Mar 2026

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 nemo-toolkit

Is nemo-toolkit safe to use?

Vulert records 11 vulnerabilities for nemo-toolkit in PyPI: 0 critical, 4 high, 1 medium and 1 low, plus 5 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 nemo-toolkit's Vulert package health score?

Vulert scores nemo-toolkit 69/100, which reads as usable, but worth attention. 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 nemo-toolkit affected?

No. 3.0.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of nemo-toolkit should I use?

3.0.0 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 nemo-toolkit have?

11 vulnerabilities are recorded for nemo-toolkit in the PyPI ecosystem: 0 critical, 4 high, 1 medium and 1 low, plus 5 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 nemo-toolkit vulnerabilities disclosed?

9 vulnerabilities were recorded for nemo-toolkit in the last 12 months, and the oldest entry in this database dates to 11 Jan 2022. 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 nemo-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 nemo-toolkit for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the nemo-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.