dbcve.org
NemoApplication · Nvidia

CVE-2025-33241

HIGH · 7.8 CVSS v3.1 Published 2026-02-18
Fix available
A fix is available. Upgrade to 2.6.1 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
NVIDIA NeMo Framework contains a vulnerability where an attacker could cause remote code execution by loading a maliciously crafted file. A successful exploit of this vulnerability might lead to code execution, escalation of privileges, information disclosure, and data tampering.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

NVIDIA NeMo Framework contains a file loading vulnerability that allows remote code execution when loading a maliciously crafted file. The vulnerability affects the file parsing/loading mechanism within the ML framework, enabling attackers to achieve code execution, privilege escalation, information disclosure, and data tampering.

MitigationAvoid loading untrusted or unverified files into the NeMo Framework until an official patch is available; implement strict input validation and file type checking on all file loading operations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
NemoApplication
Affected:< 2.6.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed NeMo Framework version
    Run 'pip show nemo' or 'pip show nemo-framework' and note the Version field, or check your dependency lock file for the nemo package version
    Affected if The version shown is lower than 2.6.1 (e.g., 2.6.0, 2.5.x, etc.)
  2. Confirm NeMo file loading is in use
    Review application logs, code, or runtime environment for usage of NeMo APIs that load files such as nemo.import_*, nemo.load, or file loading methods for configs, models, or data
    Affected if The NeMo file loading/parsing mechanism is actively used to load files from any source
  3. Inspect file loading input sources
    Audit where files loaded by NeMo originate: check if external/user-provided files are accepted, review file upload endpoints, data pipelines, or model loading workflows
    Affected if Untrusted or external files can be loaded into NeMo without prior validation
  4. Check for unverified file processing
    Examine application or system configuration for any NeMo-related file processing that lacks file type validation, signature verification, or checksum validation before loading
    Affected if Files are loaded without validation steps such as extension checking, magic byte verification, or cryptographic signatures
  5. Review NeMo deployment scope
    Identify all systems, containers, or services running NeMo Framework by searching for 'nemo' in running processes, container images, or installed packages across your infrastructure
    Affected if NeMo is deployed and exposed to external input sources or untrusted data

You are affected if NeMo Framework version is below 2.6.1 AND your environment loads external or untrusted files into the framework's parsing/loading mechanism.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.6.1 or later
Fixed in 2.6.1
Interim mitigation

Avoid loading untrusted or unverified files into the NeMo Framework until an official patch is available; implement strict input validation and file type checking on all file loading operations.

Recommended fix High confidence

Nemo Framework version 2.6.1

  1. 1. Identify the current Nemo installation method (pip, conda, docker, or source)
  2. 2. Check the current installed version using: pip show nemo-toolkit or conda list nemo
  3. 3. For pip users: Upgrade to the fixed release with: pip install --upgrade nemo-toolkit==2.6.1
  4. 4. For conda users: Update using: conda install nemo-toolkit=2.6.1
  5. 5. Verify the installation: pip show nemo-toolkit and confirm version 2.6.1 is displayed
  6. 6. Test that existing workflows function correctly after upgrade
  7. 7. Review NVIDIA NeMo Framework 2.6.1 release notes for any new dependencies or configuration changes
Caveat Review 2.6.1 release notes for potential breaking changes in APIs, dependencies, or deprecated features before upgrading production environments

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Nemo Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-33241 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-33241 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data