dbcve.org
NemoApplication · Nvidia

CVE-2025-23315

HIGH · 7.8 CVSS v3.1 Published 2025-08-26
Fix available
A fix is available. Upgrade to 2.4.0 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 for all platforms contains a vulnerability in the export and deploy component, where malicious data created by an attacker could cause a code injection issue. 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

Code injection vulnerability in NVIDIA NeMo Framework's export and deploy component where maliciously crafted data can be injected, potentially allowing arbitrary code execution, privilege escalation, information disclosure, or data tampering.

MitigationApply NVIDIA-provided security patches for NeMo Framework; until patched, disable or restrict the export/deploy functionality and validate all input data.

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

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. Confirm NeMo Framework installation
    Identify whether NVIDIA NeMo Framework is installed in your environment by checking for nemo packages, containers, or installed Python packages (e.g., pip list | grep -i nemo, docker ps, or system package listings)
    Affected if NeMo Framework is present on the system
  2. Determine installed version
    Run version check command for NeMo Framework (such as 'nemo --version', 'pip show nemo', or checking version metadata in your deployment) and compare the result to 2.4.0
    Affected if Installed version is lower than 2.4.0
  3. Verify export/deploy component is enabled
    Inspect NeMo configuration files, deployment scripts, or running services to determine if the export or deploy functionality is active, configured, or accessible
    Affected if Export/deploy component is enabled or accessible in the environment
  4. Review export/deploy data sources
    Examine any data files, configurations, or pipelines processed by the export/deploy component for the presence of untrusted or externally-sourced data that could be maliciously crafted
    Affected if Untrusted or unsanitized data is processed by the export/deploy functionality

Environment is affected if NeMo Framework version is below 2.4.0 and the export/deploy component is actively used or accessible with potentially untrusted input data.

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.4.0 or later
Fixed in 2.4.0
Interim mitigation

Apply NVIDIA-provided security patches for NeMo Framework; until patched, disable or restrict the export/deploy functionality and validate all input data.

Recommended fix Moderate confidence

Nemo 2.4.0

  1. Verify current Nemo installation version using pip show nemo or conda list nemo
  2. Backup any existing projects, configurations, and data before upgrading
  3. Upgrade Nemo to version 2.4.0 or later using: pip install --upgrade nemo-framework or pip install nemo==2.4.0
  4. If using conda, update with: conda install -c nvidia nemo=2.4.0
  5. Verify the upgrade was successful by checking: pip show nemo
  6. Test that critical functionality works as expected after upgrade

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

Fix this in Nemo Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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