CVE-2025-33253: Remote Code Execution Vulnerability in nemo-toolkit

nemo-toolkit Updated 21 Feb 2026

Summary

18/02/2026
Yes i
High
7.8

CVE-2025-33253: NVIDIA NeMo Framework Deserializes Untrusted Data. Affects nemo-toolkit versions < 2.6.1. Fixed in 2.6.1. 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 extensible architecture that allows developers to easily create and customize their AI applications. However, it is susceptible to a critical vulnerability that arises from the deserialization of untrusted data, which can be exploited by attackers.

Vulnerability Detail

NVIDIA NeMo Framework contains a vulnerability where an attacker could cause remote code execution by convincing a user to load a maliciously crafted file. This vulnerability originates from improper handling of data during the deserialization process, allowing an attacker to execute arbitrary code on the victim's machine. The consequences of a successful exploit may include code execution, denial of service, information disclosure, and data tampering, making it a significant security risk.

How To Fix

Minimum fixed version

2.6.1

This is the first release that contains the fix.

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

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

Workaround

As a temporary workaround, users should avoid loading untrusted files into the NeMo Framework until the package is updated. Additionally, implementing strict validation of input data can help reduce the risk of exploitation.

Conclusion

The vulnerability identified as CVE-2025-33253 in the NVIDIA NeMo Framework's nemo-toolkit package poses a significant risk due to its potential for remote code execution. Users are strongly advised to update to the patched version to mitigate this risk and ensure the security of their applications.

See every vulnerability recorded for nemo-toolkit →

Share this vulnerability

FAQ

CVE-2025-33253 is a vulnerability in the NVIDIA NeMo Framework's nemo-toolkit package that allows for remote code execution through the deserialization of untrusted data.

You can check if your application is affected by using the Vulert playground at Vulert Scanner, which allows you to monitor and alert for open-source vulnerabilities without requiring any signup.

The potential impacts include remote code execution, denial of service, information disclosure, and data tampering, which can severely compromise the security of affected systems.

You can update the nemo-toolkit package by running the command 'pip install --upgrade nemo-toolkit' in your terminal.

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

Minimum fixed version

2.6.1

This is the first release that contains the fix.

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

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