dbcve.org
NemoApplication · Nvidia

CVE-2025-33249

HIGH · 7.8 CVSS v3.1 Published 2026-02-18
Fix available
A fix is available. Upgrade to 2.6.1 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 voice-preprocessing script, where malicious input 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

NVIDIA NeMo Framework contains a code injection vulnerability in a voice-preprocessing script where maliciously crafted input can be executed. The vulnerability allows an attacker to potentially achieve code execution, privilege escalation, information disclosure, or data tampering through the vulnerable preprocessing component.

MitigationImplement strict input validation and sanitization on all data entering the voice preprocessing pipeline. Consider applying any available vendor patches and restricting access to the preprocessing scripts to trusted users only.

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

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. Verify NVIDIA NeMo is installed
    Run 'pip show nemo' or check your Python environment for the nemo package using 'pip list | grep -i nemo'
    Affected if The nemo package is present in the environment
  2. Check installed NeMo version
    Run 'pip show nemo' and look for the Version field, or use 'python -c "import nemo; print(nemo.__version__)"' if available
    Affected if The installed version is lower than 2.6.1 (e.g., 2.6.0, 2.5.x, etc.)
  3. Locate voice preprocessing scripts
    Search for voice preprocessing scripts in the NeMo installation directory, typically found under the nemo/collections/asr/ or nemo/collections/tts modules, or search for files containing 'voice', 'preprocess', or 'audio' in the package path
    Affected if Voice preprocessing scripts exist in the NeMo installation
  4. Identify if voice preprocessing pipeline is in use
    Inspect project code or configuration files that import or use NeMo's ASR (automatic speech recognition) or audio preprocessing modules, check for imports like 'nemo.collections.asr' or 'nemo.collections.audio'
    Affected if The project actively uses NeMo's voice/audio preprocessing components
  5. Review how input data reaches preprocessing
    Examine configuration or data loading scripts that pass audio/input data to NeMo's preprocessing pipeline, look for data flows into preprocessing functions without explicit validation
    Affected if External or untrusted input data is passed directly to the voice preprocessing component without sanitization

If NVIDIA NeMo is installed with a version below 2.6.1 AND the voice preprocessing component is actively used to process external input data, the environment is likely affected by CVE-2025-33249.

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.6.1 or later
Fixed in 2.6.1
Interim mitigation

Implement strict input validation and sanitization on all data entering the voice preprocessing pipeline. Consider applying any available vendor patches and restricting access to the preprocessing scripts to trusted users only.

Recommended fix High confidence

Nemo 2.6.1

  1. Verify current installed version of Nemo by running: pip show nemo-toolkit or pip show nemo
  2. Stop any running Nemo services or processes that use the affected version
  3. Upgrade Nemo to version 2.6.1 or later using pip: pip install --upgrade nemo-toolkit>=2.6.1
  4. Verify the upgrade was successful by running: pip show nemo-toolkit and confirming the version is 2.6.1 or higher
  5. Restart any Nemo services that were stopped

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
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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