dbcve.org
NemoApplication · Nvidia

CVE-2025-23312

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 retrieval services component, where malicious data created by an attacker could cause a code injection. 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 retrieval services component allows malicious data crafted by an attacker to trigger arbitrary code execution, potentially leading to privilege escalation, information disclosure, or data tampering.

MitigationImplement strict input validation and sanitization in the retrieval services component; apply vendor patches when released; restrict retrieval service permissions to least privilege.

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 NVIDIA NeMo installation
    Check for NeMo package via pip list | grep -i nemo or check for nemo directories in the Python environment (commonly at ~/.cache/torch/hub/nemo or within the nemo-legacy package directory)
    Affected if NeMo framework is installed on the system
  2. Identify installed NeMo version
    Run: python -c 'import nemo; print(nemo.__version__)' or check the installed package version with pip show nemo-legacy
    Affected if The version is lower than 2.4.0 (e.g., 2.3.0, 2.2.0, 1.x, etc.)
  3. Locate retrieval services configuration
    Search for retrieval-related config files or modules in the NeMo deployment: grep -r 'retrieval' /path/to/nemo/config/ or inspect the deployed application YAML files if NeMo is deployed as a service
    Affected if Retrieval services component is configured or enabled in the deployment
  4. Verify retrieval service is exposed or in use
    Check running processes or services that utilize retrieval vector store or RAG (retrieval-augmented generation) modules: ps aux | grep -i nemo, or inspect any API endpoints exposing retrieval functionality
    Affected if Retrieval services are actively running or exposed as an API/service

You are affected if NVIDIA NeMo is installed with a version below 2.4.0 AND the retrieval services component is enabled or in use in your environment.

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

Implement strict input validation and sanitization in the retrieval services component; apply vendor patches when released; restrict retrieval service permissions to least privilege.

Recommended fix Moderate confidence

2.4.0 or later

  1. Check current installed version of Nemo (e.g., pip show nemo or conda list nemo)
  2. Upgrade Nemo to version 2.4.0 or later using your package manager (e.g., pip install --upgrade nemo or conda update nemo)
  3. Verify the new version is installed (pip show nemo)
  4. Restart any running NeMo services or containers to load the updated version
  5. Test that the retrieval services component functions correctly after the 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
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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