dbcve.org
NemoApplication · Nvidia

CVE-2025-33226

HIGH · 7.8 CVSS v3.1 Published 2025-12-16
Fix available
A fix is available. Upgrade to 2.5.3 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 where malicious data created by an attacker may cause a code injection. 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 code injection vulnerability where malicious data crafted by an attacker can be processed in an unsafe manner, potentially allowing arbitrary code execution, privilege escalation, information disclosure, and data tampering. The vulnerability affects all platform versions of the framework.

MitigationApply vendor-supplied patches when available; implement strict input validation and sanitization on all data ingestion points within the NeMo Framework; conduct security code review of data processing pipelines.

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

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. Identify if NVIDIA NeMo Framework is installed
    Run 'pip list | grep -i nemo' or check for NeMo package directories in your Python environment (e.g., looking for nemo or nem框架-related packages)
    Affected if NeMo Framework package is present on the system
  2. Determine installed NeMo version
    Execute 'pip show nemo' or 'python -c "import nemo; print(nemo.__version__)"' to retrieve the installed version number
    Affected if The reported version is less than 2.5.3 (e.g., 2.5.0, 2.4.0, etc.)
  3. Check for data ingestion pipelines
    Review your NeMo-based application code and configuration files for data loading/processing components such as data loaders, parsers, or pipeline configuration files that handle external input
    Affected if The system uses NeMo data pipelines that process external or untrusted data without validation
  4. Inspect data processing configurations
    Examine NeMo configuration files (typically .yaml or .json) for data processing settings, especially any 'data_pipeline', 'data_loader', or 'preprocessing' configurations
    Affected if Data processing configurations accept raw input without evident sanitization routines

You are affected if NVIDIA NeMo Framework is installed and the installed version is below 2.5.3, particularly if the system uses NeMo to process external or untrusted 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.5.3 or later
Fixed in 2.5.3
Interim mitigation

Apply vendor-supplied patches when available; implement strict input validation and sanitization on all data ingestion points within the NeMo Framework; conduct security code review of data processing pipelines.

Recommended fix High confidence

2.5.3

  1. 1. Check the currently installed NeMo version by running: pip show nemo-toolkit or import nemo; print(nemo.__version__)
  2. 2. Upgrade to the fixed version by running: pip install --upgrade nemo-toolkit==2.5.3 (or pip install --upgrade nemo for the full framework)
  3. 3. Verify the installation was successful by checking the version again with pip show nemo-toolkit
  4. 4. If using a virtual environment or container, ensure the environment is rebuilt/refreshed to load the updated package

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

Fix this in Nemo Scoped from the published advisory
  • Consultation12.0 h
  • Implementation32.0 h
  • Testing20.0 h
  • Review / QA12.0 h
76.0 hours of engineering $13,320
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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