CVE-2026-24159: Remote Code Execution Vulnerability in NVIDIA NeMo Framework (nemo-toolkit)

nemo-toolkit Updated 02 Apr 2026

Summary

24/03/2026
Yes i
High
7.8

CVE-2026-24159: NVIDIA NeMo Framework contains a vulnerability leading to Remote Code Execution. Affects nemo-toolkit versions < 2.6.2. Fixed in 2.6.2. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The NVIDIA NeMo Framework, specifically the nemo-toolkit package, is a powerful tool designed for building and training state-of-the-art conversational AI models. It provides a flexible and modular architecture that allows developers to create, customize, and deploy AI models efficiently. However, the framework has been found to contain a significant vulnerability that could potentially allow attackers to execute arbitrary code remotely.

Vulnerability Detail

The vulnerability in the NVIDIA NeMo Framework arises from improper handling of certain inputs, which may allow an attacker to execute arbitrary code on the server. This could lead to severe consequences, including unauthorized access to sensitive data, privilege escalation, and data tampering. The vulnerability is classified under CWE-502, indicating issues related to deserialization of untrusted data. The potential impact of this vulnerability is high, as it could compromise the integrity and confidentiality of the system.

How To Fix

Latest published version: 3.0.0 as of 23 Oct 2026

pip install --upgrade "nemo-toolkit==3.0.0"

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2.6.2

This is the first release that contains the fix.

pip install --upgrade "nemo-toolkit==2.6.2"

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a temporary workaround, you can restrict access to the affected components of the NVIDIA NeMo Framework until the package is updated. This may involve modifying firewall rules or access controls to limit exposure to untrusted users.

Conclusion

The NVIDIA NeMo Framework's vulnerability (CVE-2026-24159) poses a significant risk due to its potential for remote code execution. It is crucial for users to update to the patched version (2.6.2) to mitigate this risk. Implementing workarounds and monitoring for vulnerabilities can help protect systems until updates are applied.

See every vulnerability recorded for nemo-toolkit →

Share this vulnerability

FAQ

CVE-2026-24159 is a vulnerability in the NVIDIA NeMo Framework that allows for remote code execution due to improper input handling.

Exploiting this vulnerability could lead to unauthorized code execution, privilege escalation, data tampering, and information disclosure.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

If immediate updates are not possible, consider implementing access restrictions or monitoring for suspicious activity as a temporary measure.

The CVSS score of this vulnerability is 7.8, indicating a high severity level.

Related vulnerabilities

Recent vulnerabilities recorded for nemo-toolkit.

How To Fix

Latest published version: 3.0.0 as of 23 Oct 2026

pip install --upgrade "nemo-toolkit==3.0.0"

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2.6.2

This is the first release that contains the fix.

pip install --upgrade "nemo-toolkit==2.6.2"

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

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 →
Help improve this record
Report an issue or send feedback