dbcve.org
Megatron LmApplication · Nvidia

CVE-2025-23306

HIGH · 7.8 CVSS v3.1 Published 2025-08-13
Fix available
A fix is available. Upgrade to 0.12.2 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 megatron/training/ arguments.py component where an attacker could cause a code injection issue by providing a malicious input. 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 megatron/training/arguments.py where malicious input is not properly validated before use, potentially allowing arbitrary code execution, privilege escalation, or data tampering.

MitigationSanitize and validate all user-provided input in arguments.py; remove any use of unsafe functions like eval() or exec() that process input strings as code; implement allowlist-based input validation.

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

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 megatron' to see the installed version number
    Affected if Version is lower than 0.12.2
  2. Locate arguments.py in the megatron installation
    Find the file: pip show megatron-lm to get install location, then navigate to megatron/training/arguments.py
    Affected if File exists in the installation
  3. Inspect arguments.py for unsafe functions
    Open arguments.py and search for 'eval(' or 'exec(' function calls within the file
    Affected if eval() or exec() functions are present and process user-provided input
  4. Check input validation around eval/exec calls
    Review the code context around any eval/exec calls to see if user-supplied arguments (like command-line args, config values, or environment variables) flow directly into these functions without sanitization
    Affected if User input parameters are passed to eval/exec without validation or sanitization
  5. Verify if affected code paths are reachable
    Determine if the vulnerable code in arguments.py is actually used in your workflows (e.g., via training scripts that parse command-line arguments)
    Affected if Your training pipeline invokes code paths in arguments.py that use unvalidated input with eval/exec

You are affected if Megatron-LM version is below 0.12.2 AND your installation contains eval/exec calls in arguments.py that process unvalidated user input.

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.2 or later
Fixed in 0.12.2
Interim mitigation

Sanitize and validate all user-provided input in arguments.py; remove any use of unsafe functions like eval() or exec() that process input strings as code; implement allowlist-based input validation.

Recommended fix High confidence

0.12.2

  1. 1. Back up your current Megatron-LM installation and any custom configurations.
  2. 2. Upgrade Megatron-LM to version 0.12.2 or later using your package manager (e.g., pip install --upgrade megatron-lm) or by pulling the specific version from the repository.
  3. 3. Verify the installed version matches or exceeds 0.12.2 using: pip show megatron-lm or equivalent version check.
  4. 4. Test your workloads to confirm the upgrade does not break existing functionality.
  5. 5. If using a requirements.txt or dependency lock file, update the megatron-lm version specification to >= 0.12.2.
Caveat Review release notes between your current version and 0.12.2 for any API or behavior changes that may affect existing training scripts or configurations.

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

Fix this in Megatron Lm Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
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,992.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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