dbcve.org
Megatron LmApplication · Nvidia

CVE-2025-23354

HIGH · 7.8 CVSS v3.1 Published 2025-09-24
Fix available
A fix is available. Upgrade to 0.12.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 Megatron-LM for all platforms contains a vulnerability in the ensemble_classifer script where malicious data created by an attacker may cause an 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 Megatron-LM contains an injection vulnerability in the ensemble_classifer script where malicious data crafted by an attacker can lead to code execution, privilege escalation, information disclosure, and data tampering. The vulnerability stems from insufficient input validation or sanitization of data processed by this script.

MitigationImplement rigorous input validation and sanitization on all data processed by the ensemble_classifer script, preferably using allowlist validation and parameterized processing methods. Review and audit data flow through the script for additional injection points.

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
Megatron LmApplication
Affected:< 0.12.3= 0.13.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 installed Megatron-LM version
    Run 'pip show megatron-lm' or check the version in your environment's package manager to identify the installed version
    Affected if The installed version is less than 0.12.3 or exactly 0.13.0
  2. Locate the ensemble_classifer script
    Search for 'ensemble_classifer.py' in the Megatron-LM installation directory, typically found in the tools or scripts folder of the repository
    Affected if The script exists in your installation and the version is vulnerable
  3. Verify if ensemble_classifer is used with external data
    Inspect any automation, pipelines, or scripts that invoke ensemble_classifer and determine whether they process data from untrusted sources such as user input, external files, or network endpoints
    Affected if The script processes data from untrusted or external sources without validation
  4. Check input validation on ensemble_classifer execution
    Review how ensemble_classifer is invoked in your workflows - examine command-line arguments, config files, or API calls passed to the script for any user-controlled or external data
    Affected if Data passed to ensemble_classifer lacks sanitization or allowlist validation before processing
  5. Audit file permissions on ensemble_classifer
    Verify file ownership and permissions on the ensemble_classifer script to ensure it cannot be modified by unauthorized users
    Affected if The script has overly permissive access allowing modification by non-privileged users

You are affected if your Megatron-LM version is below 0.12.3 or exactly 0.13.0 AND the ensemble_classifer script processes external or unsanitized data 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 0.12.3 or later
Fixed in 0.12.3
Interim mitigation

Implement rigorous input validation and sanitization on all data processed by the ensemble_classifer script, preferably using allowlist validation and parameterized processing methods. Review and audit data flow through the script for additional injection points.

Recommended fix Moderate confidence

Upgrade to Megatron LM version 0.13.1 or later (or the latest stable release)

  1. 1. Identify the currently installed Megatron LM version using pip show megatron-lm or checking your requirements.txt
  2. 2. If running a version less than 0.12.3 or exactly version 0.13.0, plan for upgrade
  3. 3. Create a backup of your current environment and project configurations
  4. 4. Upgrade Megatron LM using: pip install --upgrade megatron-lm
  5. 5. Verify the new version is installed: pip show megatron-lm
  6. 6. Test your ensemble_classifier script functionality to ensure the upgrade does not break existing workflows
  7. 7. If using a framework that pins specific versions, update requirements.txt or environment specifications to reflect the fixed version
Caveat Review release notes between your current version and the target version for any API changes or deprecated features in the ensemble_classifier script

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

Fix this in Megatron Lm Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
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,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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