dbcve.org
NemoApplication · Nvidia

CVE-2025-23251

CRITICAL · 9.8 CVSS v3.1 Published 2025-04-22
Fix available
A fix is available. Upgrade to 25.02 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 Framework contains a vulnerability where a user could cause an improper control of generation of code by remote code execution. A successful exploit of this vulnerability might lead to 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 Framework contains an improper control of code generation vulnerability that allows authenticated attackers to execute arbitrary code remotely. The vulnerability stems from insufficient controls over code generation mechanisms within the framework, potentially through unsafe evaluation of user-controlled input as executable code.

MitigationApply NVIDIA's security patch for this vulnerability immediately; until patched, restrict network access to NeMo Framework services and enforce strict authentication. Consider disabling dynamic code generation features if possible.

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:< 25.02

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. Identify NeMo Framework installation
    Run 'pip show nemo' or 'pip list | grep -i nemo' to find the installed NeMo package and version
    Affected if The installed version is lower than 25.02 (e.g., 24.x, 1.x series, or version not shown)
  2. Verify NeMo version via Python import
    Execute 'python -c "import nemo; print(nemo.__version__)"' or check the version attribute if accessible
    Affected if The returned version is missing, undefined, or less than 25.02
  3. Inspect NeMo configuration for code generation settings
    Check nemo configuration files (typically in ~/.nemo or project config directories) for any code generation, code execution, or dynamic evaluation settings
    Affected if Configuration enables dynamic code generation, eval(), exec(), or similar runtime code execution features
  4. Review application logs for code generation activity
    Search NeMo application logs for patterns related to code generation, model-based code writing, or dynamic code construction
    Affected if The application uses or logs any code generation capabilities that could be exploited
  5. Check for custom code generation modules
    Inspect the NeMo deployment for any custom code that invokes dynamic code execution functions (eval, exec, compile, __import__) in conjunction with NeMo APIs
    Affected if Custom code that interfaces with NeMo's code generation features is present and uses unsafe dynamic execution

The environment is affected if NeMo Framework version is below 25.02 AND the code generation feature or dynamic code execution capabilities are in use.

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 25.02 or later
Fixed in 25.02
Interim mitigation

Apply NVIDIA's security patch for this vulnerability immediately; until patched, restrict network access to NeMo Framework services and enforce strict authentication. Consider disabling dynamic code generation features if possible.

Recommended fix Moderate confidence

25.02

  1. 1. Identify the current installed version of NVIDIA NeMo Framework by checking your environment or running: pip show nemo or checking your container image tag
  2. 2. If the installed version is below 25.02, plan for upgrade during a maintenance window
  3. 3. Backup any custom configurations, models, and data associated with your NeMo deployment
  4. 4. For pip-based installations, upgrade using: pip install --upgrade nemo==25.02 or pip install nemo==25.02
  5. 5. For containerized deployments, pull the updated container image tagged with version 25.02 from NVIDIA NGC or your registry
  6. 6. After upgrade, verify the installation by running: pip show nemo and confirming the version displays 25.02
  7. 7. Test critical functionality to ensure the upgrade did not break existing workflows
  8. 8. Consult NVIDIA NeMo Framework 25.02 release notes for any migration-specific considerations
Caveat Review 25.02 release notes for any API changes or backward compatibility considerations before upgrading production systems

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

Fix this in Nemo Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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