dbcve.org
Nemo CuratorApplication · Nvidia

CVE-2025-23307

HIGH · 7.8 CVSS v3.1 Published 2025-08-26
Fix available
A fix is available. Upgrade to 25.07 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 Curator for all platforms contains a vulnerability where a malicious file created by an attacker could allow 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 Curator contains a code injection vulnerability where an attacker can craft a malicious file that, when processed by the software, allows injection and execution of arbitrary code. Successful exploitation enables code execution, privilege escalation, information disclosure, and data tampering.

MitigationRemediate by implementing strict input validation and sanitization for all file processing operations, using safe parsing methods, and restricting file types accepted by the application.

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
Nemo CuratorApplication
Affected:< 25.07

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 NeMo Curator installation
    Check if NVIDIA NeMo Curator is present in the environment by searching for nemo_curator package or installed Python module using 'pip list' or 'conda list' commands.
    Affected if NeMo Curator is installed and running in the environment.
  2. Identify installed version
    Run 'pip show nemo-curator' or 'conda list nemo-curator' to retrieve the installed version number. Alternatively, import the module in Python and query its __version__ attribute if available.
    Affected if The installed version number is lower than 25.07.
  3. Verify file processing capability is enabled
    Review application configuration files, scripts, or workflow definitions that import and use nemo_curator modules for data processing (e.g., from nemo_curator import...). Check for any pipeline configurations that process input files.
    Affected if The application imports and uses NeMo Curator's file processing functions to handle external data files.
  4. Inspect file type restrictions
    Review any configuration or code that defines accepted file types or input sources for NeMo Curator processing. Look for explicit allowlists or validation logic around file imports.
    Affected if No strict file type validation or allowlisting is configured for processed files.

You are affected if NeMo Curator is installed with a version below 25.07 AND the file processing features are actively used to process input data files.

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.07 or later
Fixed in 25.07
Interim mitigation

Remediate by implementing strict input validation and sanitization for all file processing operations, using safe parsing methods, and restricting file types accepted by the application.

Recommended fix High confidence

Nemo Curator 25.07

  1. 1. Identify the current installed version of NVIDIA NeMo Curator (e.g., run 'pip show nemo-curator' or check your environment's package list)
  2. 2. Create a backup of any existing configurations, custom scripts, and data used by NeMo Curator
  3. 3. Upgrade to version 25.07 or later using your package manager (e.g., 'pip install --upgrade nemo-curator>=25.07' or 'conda install nemo-curator>=25.07')
  4. 4. Verify the upgrade was successful by checking the installed version matches or exceeds 25.07
  5. 5. Test that your existing workflows and pipelines function correctly after the upgrade

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

Fix this in Nemo Curator Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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