dbcve.org
Megatron LmApplication · Nvidia

CVE-2025-23265

HIGH · 7.8 CVSS v3.1 Published 2025-06-24
Fix available
A fix is available. Upgrade to 0.12.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 Megatron-LM for all platforms contains a vulnerability in a python component where an attacker may cause a code injection issue by providing a malicious file. 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 a code injection vulnerability in a Python component where an attacker can provide a malicious file to execute arbitrary code. Successful exploitation allows code execution, privilege escalation, information disclosure, and data tampering.

MitigationImplement strict input validation and sanitization for file handling in Python components; avoid unsafe use of eval(), exec(), or dynamic imports with untrusted data; apply principle of least privilege for file operations.

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.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. Check installed Megatron-LM version
    Run 'pip show megatron-lm' or 'pip list | grep -i megatron' to find the installed version number
    Affected if Version is lower than 0.12.1
  2. Locate Python file handling components
    Search the Megatron-LM installation directory for Python files that handle file input, such as: find $(python -c 'import megatron; print(megatron.__path__[0])') -name '*.py' -exec grep -l 'exec\|eval\|__import__\|load' {} \;
    Affected if Files containing unsafe file-to-code operations (eval, exec, dynamic imports) are present in the installation
  3. Inspect file loading logic for dynamic execution
    Review any code that reads a file and passes its contents to eval(), exec(), or uses __import__() with file-derived data
    Affected if The code loads external files and executes their contents without validation
  4. Check for untrusted file input pathways
    Examine whether your workflows pass user-supplied, externally sourced, or network-received files to Megatron-LM components for processing
    Affected if Untrusted files are processed by Megatron-LM's Python components
  5. Verify environment exposure
    Determine if the Megatron-LM deployment has network access or accepts file uploads from untrusted sources
    Affected if The environment can receive or load files from untrusted sources into Megatron-LM

You are affected if Megatron-LM version is below 0.12.1 AND your environment processes external or untrusted files through the vulnerable Python file handling component.

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.1 or later
Fixed in 0.12.1
Interim mitigation

Implement strict input validation and sanitization for file handling in Python components; avoid unsafe use of eval(), exec(), or dynamic imports with untrusted data; apply principle of least privilege for file operations.

Recommended fix Moderate confidence

0.12.1 or later

  1. Upgrade Megatron-LM to version 0.12.1 or later to resolve the code injection vulnerability.
  2. Verify the installation by checking the installed version using pip show megatron-lm or equivalent package manager.
  3. If using in a project, update the dependency specification to require megatron-lm>=0.12.1.
  4. After upgrading, test the application to ensure functionality remains intact.

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
  • Testing4.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,560
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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