CVE-2025-23353
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 · uneditedNVIDIA Megatron-LM for all platforms contains a vulnerability in the msdp preprocessing 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 confidenceNVIDIA Megatron-LM contains an injection vulnerability in the msdp preprocessing script where attacker-controlled malicious data can be processed without proper sanitization, leading to code execution, privilege escalation, information disclosure, or data tampering.
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< 0.12.3= 0.13.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Megatron-LM versionRun 'pip show megatron-lm' or check the package version in your environment (e.g., pip list | grep megatron)Affected if Version is lower than 0.12.3 or equals exactly 0.13.0
-
Identify msdp preprocessing script usageSearch for 'msdp' in your project codebase, configuration files, or imported modules (e.g., grep -r 'msdp' or inspect import statements)Affected if The msdp preprocessing script or module is present and being used in your pipeline
-
Check for unsanitized data input to msdpReview data processing code that feeds into msdp; look for direct variable interpolation, command execution, or string formatting without sanitization (e.g., inspect preprocessing functions that pass external data to msdp)Affected if External or user-controlled data is passed directly to msdp without validation, sanitization, or parameterization
You are affected if your Megatron-LM version is < 0.12.3 or = 0.13.0 AND the msdp preprocessing script is in use with unsanitized data flowing into it
Generated from the published advisory. Verify against your own configuration.
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 · scoped0.12.3
Implement strict input validation and sanitization on all data flowing into the msdp preprocessing script; use parameterized processing or sandboxing to prevent injection attacks.
0.12.3 (for <0.12.3) or 0.13.1+ (for 0.13.0)
- 1. Identify current installed version of Megatron-LM using pip show megatron-lm or checking requirements files
- 2. For systems on versions < 0.12.3: Upgrade to version 0.12.3 or later by running: pip install megatron-lm>=0.12.3
- 3. For systems on version 0.13.0: Upgrade to version 0.13.1 or later by running: pip install megatron-lm>=0.13.1
- 4. Verify the upgrade was successful: pip show megatron-lm to confirm the installed version
- 5. Test that msdp preprocessing functionality works as expected with the new version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-23353 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-23353 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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