NVIDIA NeMo Framework Contains a Vulnerability
Source GCVE Database
Not known to be exploited · CVSS 7.3 High : upgrade to 2.5.1 soon.
Data as of 19 Nov 2026, 02:16 UTC
- Patch
- Available – fixed in 2.5.1
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 25 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Upgrade nvidia-nemo to 2.5.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
PyPInvidia-nemopkg:pypi/nvidia-nemoOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
If you cannot patch yet, limit exposure by restricting access to the NVIDIA NeMo framework and avoid executing untrusted input that could influence predefined variables.
Description
The NVIDIA NeMo framework has a vulnerability involving a predefined variable that allows an attacker to include functionality from an untrusted control sphere. Exploiting this flaw could lead to code execution with high impact on confidentiality, integrity, and availability.