dbcve.org
Megatron LmApplication · Nvidia

CVE-2025-23264

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 its Python component where processing a malicious file allows attackers to execute arbitrary code. The vulnerability stems from unsafe use of dynamic code execution functions (likely eval/exec) or insecure deserialization when parsing input files, enabling full system compromise.

MitigationUpgrade to the vendor-provided patched version of Megatron-LM. If a patch is unavailable, audit all file parsing code paths and replace unsafe eval/exec calls or insecure deserialization with safe alternatives such as ast.literal_eval or structured data formats with schema 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.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. Identify Megatron-LM installation and version
    Run 'pip show megatron-lm' or check your environment's installed packages list to find the installed version of Megatron-LM
    Affected if The installed version is lower than 0.12.1 (e.g., 0.12.0, 0.11.0, or any version before 0.12.1)
  2. Locate file parsing code in the Megatron-LM installation
    Search the Megatron-LM source directory for Python files that handle file input, particularly those using eval(), exec(), pickle, yaml.load, or similar deserialization functions
    Affected if The codebase contains file parsing logic that uses unsafe eval/exec calls or insecure deserialization without proper input validation
  3. Identify data loading and model input processing
    Examine data loading scripts, tokenizer configuration loaders, or checkpoint loading code that processes external files or serialized data
    Affected if The system loads checkpoint files, tokenizer definitions, or training data from untrusted sources using vulnerable deserialization patterns
  4. Review custom model or configuration loading
    Check if your deployment uses any custom code that loads configuration files, model weights, or training hyperparameters from user-supplied files processed by Megatron-LM
    Affected if Your environment processes custom or third-party files through Megatron-LM's parsing functions without sanitization

You are affected if Megatron-LM version is below 0.12.1 AND your environment processes external files through the vulnerable parsing code paths.

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

Upgrade to the vendor-provided patched version of Megatron-LM. If a patch is unavailable, audit all file parsing code paths and replace unsafe eval/exec calls or insecure deserialization with safe alternatives such as ast.literal_eval or structured data formats with schema validation.

Recommended fix Moderate confidence

megatron-lm version 0.12.1 or later

  1. 1. Identify all deployments or environments running Megatron LM versions prior to 0.12.1
  2. 2. Review the application's file loading mechanisms to understand the attack vector for code injection
  3. 3. Upgrade Megatron LM to version 0.12.1 or later by updating the package: pip install megatron-lm==0.12.1 (or newer if available)
  4. 4. If using a containerized deployment, rebuild images with the updated version
  5. 5. After upgrading, verify that the application functions correctly with the new version
  6. 6. Test the fix by ensuring malicious files cannot be executed through the vulnerable component
Caveat Review release notes for any API changes between your current version and 0.12.1; minor version upgrades typically have limited breaking changes but custom integrations should be tested

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 / QA3.0 h
19.0 hours of engineering $3,380
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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