dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-24149

HIGH · 7.8 CVSS v3.1 Published 2026-02-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 script, where malicious data created by an attacker may cause a code injection issue. A successful exploit of this vulnerability may lead to code execution, escalation of privileges, information disclosure, 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 one of its scripts where attacker-controlled malicious data can be leveraged to inject and execute arbitrary code. The vulnerability stems from insufficient input sanitization or validation within the script, allowing an attacker to manipulate data inputs to achieve code execution, privilege escalation, information disclosure, or data tampering.

MitigationApply the official NVIDIA patch when available. In the interim, review and harden scripts that process external or user-controlled data, implement strict input validation, and restrict script execution permissions to limit exposure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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 if NVIDIA Megatron-LM is installed
    Locate the Megatron-LM installation directory and check for the presence of the framework. Common locations include pip-installed packages (pip show megatron-lm), Git repositories cloned locally, or container images. Obtain the version if available.
    Affected if Megatron-LM is present and the installed version is within the affected range (if a version range becomes known from NVIDIA's advisory).
  2. Locate scripts that process external or user-controlled data
    Review the Megatron-LM codebase for scripts that accept input from users, external files, environment variables, or network sources. Focus on Python scripts (.py files) that handle data loading, configuration parsing, or model inference.
    Affected if Such scripts exist and handle data without explicit indication of sanitization.
  3. Inspect scripts for input validation and sanitization
    Examine the identified scripts for proper input validation functions, sanitization routines, or use of safe APIs (such as ast.literal_eval instead of eval, or parameterized operations instead of string concatenation for commands). Look for patterns like direct use of exec(), eval(), os.system(), or string formatting in SQL/command contexts.
    Affected if The scripts lack proper input validation, use unsafe functions, or construct commands/data from raw input without sanitization.
  4. Check execution permissions on scripts
    Review file permissions on scripts within the Megatron-LM installation. Determine if scripts are executable by unprivileged users and if they run with elevated privileges.
    Affected if Scripts handling external data have overly permissive execution rights, allowing manipulation of data inputs to trigger the injection.
  5. Review data input sources
    Identify what external data sources feed into the vulnerable scripts: user-provided config files, model weights from untrusted sources, log files, environment variables, or API inputs. Document which data paths are accessible to untrusted users.
    Affected if External or user-controlled data can reach the scripts without validation checks in place.

You are affected if NVIDIA Megatron-LM is installed and contains scripts that process external or user-controlled data without proper input validation or sanitization, allowing an attacker to inject arbitrary code.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the official NVIDIA patch when available. In the interim, review and harden scripts that process external or user-controlled data, implement strict input validation, and restrict script execution permissions to limit exposure.

Have this fixed 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 help mitigating

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-2026-24149 — 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-2026-24149 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