CVE-2025-33205
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 NeMo framework contains a vulnerability in a predefined variable, where an attacker could cause inclusion of functionality from an untrusted control sphere by use of a predefined variable. A successful exploit of this vulnerability may lead to code execution.
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 · high confidenceNVIDIA NeMo framework contains a variable-based inclusion vulnerability where a predefined variable can be manipulated to include functionality from an untrusted source, potentially allowing remote code execution.
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< 2.5.1CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/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.
-
Identify NeMo framework installation versionRun `pip show nemo` or `pip show nemo-framework` and note the Version field. Alternatively, check the version in your environment's package metadata.Affected if The installed version is lower than 2.5.1 (e.g., 2.5.0, 2.4.0, etc.)
-
Locate code with dynamic inclusion functionalitySearch source files for patterns such as `include`, `__import__`, `exec`, `eval`, or similar constructs that accept variable input. Focus on Python files within the NeMo installation directory.Affected if The codebase contains inclusion logic that uses user-controllable or environment-based variables without strict validation.
-
Identify the predefined inclusion variableReview application configuration files, environment variables, and initialization scripts to locate variables that control inclusion paths or module loading. Look for variables named similarly to those mentioned in deployment documentation.Affected if A predefined variable exists that can be set to an arbitrary value pointing to an untrusted source or path.
-
Verify inclusion target allowlisting statusExamine configuration files and code that handle inclusion targets. Determine whether an allowlist or blocklist is enforced, and whether it can be bypassed.Affected if No strict allowlist is implemented, or the allowlist validation can be circumvented allowing arbitrary inclusion targets.
Your environment is affected if NeMo version is below 2.5.1 AND a variable controlling dynamic inclusion can be manipulated to reference an untrusted source.
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 · scoped2.5.1
Restrict or validate the predefined variable to prevent control sphere manipulation; implement strict allowlisting of permitted inclusion targets and disable dynamic inclusion capabilities.
2.5.1 or later
- Upgrade NVIDIA NeMo framework to version 2.5.1 or later
- Verify the installed version matches or exceeds 2.5.1 using the package manager or framework version check
- Test critical application functionality after upgrade to ensure compatibility
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-33205 — 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-33205 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