dbcve.org
NemoApplication · Nvidia

CVE-2025-23361

HIGH · 7.8 CVSS v3.1 Published 2025-11-11
Fix available
A fix is available. Upgrade to 2.5.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 a script, where malicious input created by an attacker may cause improper control of code generation. A successful exploit of this vulnerability may 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 vulnerability in a script where malicious attacker-crafted input can cause improper control of code generation, potentially allowing code execution, privilege escalation, information disclosure, and data tampering.

MitigationImplement strict input validation and sanitization on the affected script to prevent injection of malicious code; restrict or sandbox code generation functions.

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.5.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. Check if NVIDIA NeMo is installed
    Run 'pip show nemo' or look for NeMo packages in your Python environment using 'pip list | grep -i nemo'
    Affected if NeMo is not found in the environment, the check does not apply
  2. Determine the installed NeMo version
    Run 'pip show nemo' and note the Version field, or use 'python -c "import nemo; print(nemo.__version__)"' if available
    Affected if The installed version is lower than 2.5.0 (e.g., 2.4.0, 2.0.0, 1.x)
  3. Identify scripts or modules related to code generation
    Search for scripts in the NeMo installation directory that handle code generation, dynamic code execution, or template processing. Look in the 'scripts' or 'nemo/utils' directories within the NeMo package
    Affected if Scripts that perform dynamic code generation or template processing are present in the NeMo installation
  4. Check if code generation features are enabled in configuration
    Review NeMo configuration files (YAML/JSON) for settings related to code generation, script execution, or dynamic code handling. Look for flags like 'allow_code_execution', 'dynamic_generation', or similar
    Affected if Configuration enables dynamic code generation, script execution from user input, or lacks input validation controls
  5. Inspect the specific vulnerable script for presence and configuration
    Locate and examine the script identified as vulnerable to improper control of code generation. Check its permissions, input handling parameters, and whether it accepts external or user-controlled input
    Affected if The vulnerable script exists and is configured to accept unvalidated external input

You are affected if NeMo version is below 2.5.0 AND code generation scripts that accept user input are present and enabled 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.5.0 or later
Fixed in 2.5.0
Interim mitigation

Implement strict input validation and sanitization on the affected script to prevent injection of malicious code; restrict or sandbox code generation functions.

Recommended fix High confidence

2.5.0

  1. Verify current Nemo installation version using 'pip show nemo' or equivalent package manager
  2. Backup any existing projects, configurations, and data that interact with the NeMo Framework
  3. Upgrade Nemo to version 2.5.0 or later using pip: pip install --upgrade nemo or pip install nemo==2.5.0
  4. Verify the upgrade was successful by checking the installed version: pip show nemo
  5. Test critical functionality to ensure the upgrade does not break existing workflows
  6. Review NeMo Framework release notes for 2.5.0 for any additional post-upgrade configuration requirements
Caveat Review release notes for potential API or compatibility changes 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
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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