dbcve.org
NemoApplication · Nvidia

CVE-2025-23304

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-13
Fix available
A fix is available. Upgrade to 2.3.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 library for all platforms contains a vulnerability in the model loading component, where an attacker could cause code injection by loading .nemo files with maliciously crafted metadata. A successful exploit of this vulnerability may lead to remote code execution 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 library contains a code injection vulnerability in its model loading component. Attackers can craft malicious .nemo files with specially designed metadata that gets deserialized/parsed unsafely, allowing arbitrary code execution when the model is loaded.

MitigationAvoid loading .nemo files from untrusted sources and apply NVIDIA's official patch when available. Implement file validation and consider sandboxing model loading operations until the vulnerability is remediated.

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.3.2

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Check installed NeMo version
    Run 'pip show nemo-toolkit' or 'pip show nemo' to retrieve the installed version number, or check your environment's package manifest
    Affected if The installed version is below 2.3.2
  2. Identify NeMo model loading usage
    Search your codebase or application logs for imports of nemo.model_loading modules, or for calls that load .nemo files such as nemo.restore_from() or similar model loading functions
    Affected if Your application or workflow loads .nemo model files using NeMo's model loading component
  3. Check for .nemo file processing in your pipelines
    Inspect any data processing pipelines, scripts, or services that accept .nemo files as input, particularly where automatic loading or deserialization occurs
    Affected if Your environment automatically loads .nemo files from potentially untrusted sources without validation
  4. Review model deserialization configuration
    Examine NeMo configuration files or environment variables related to model loading, deserialization, and metadata parsing settings
    Affected if Model deserialization is configured to process metadata from .nemo files without additional validation layers

You are affected if NeMo version is below 2.3.2 AND your environment loads or processes .nemo files using the vulnerable model loading component.

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.3.2 or later
Fixed in 2.3.2
Interim mitigation

Avoid loading .nemo files from untrusted sources and apply NVIDIA's official patch when available. Implement file validation and consider sandboxing model loading operations until the vulnerability is remediated.

Recommended fix High confidence

NeMo version 2.3.2 or later

  1. Check the currently installed NeMo version using pip list | grep nemo or import nemo; print(nemo.__version__)
  2. Upgrade to NeMo version 2.3.2 or later using: pip install --upgrade nemo-toolkit or pip install nemo-toolkit>=2.3.2
  3. Verify the upgrade was successful by checking the installed version again
  4. If using in a project, update any version pinning in requirements.txt or setup.py to require nemo-toolkit>=2.3.2
  5. After upgrading, test that legitimate .nemo model loading functionality still works as expected

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

Fix this in Nemo Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
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,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-23304 — 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-23304 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