CVE-2025-33250 json
NVIDIA NeMo Framework contains a vulnerability where an attacker could cause remote code execution.
published 2026-02-18 8 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-207814
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 17%
- public exploits
- 0
- none known
Summary
NVIDIA NeMo Framework contains a vulnerability where an attacker could cause remote code execution. A successful exploit of this vulnerability might lead to code execution, denial of service, information disclosure, and data tampering.
Patch / fix
- nvidia nemo 2.6.1
- nvidia nemo_framework 2.6.1
- nvidia nvidia_nemo_framework 2.6.1
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 8 mo ago
Exploit prediction
0.25% chance of exploitation in the next 30 days, higher than 17% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- NVIDIA NeMo Framework
Classification
- Weakness
-
- CWE-94 Improper Control of Generation of Code
References
-
nvidia.custhelp.com
/app/answers/detail/a_id/5762
vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2025-33250
us-government-resource, vdb-entry
-
cve.org
/CVERecord?id=CVE-2025-33250
third-party-advisory
Sources
- CVE List CVE-2025-33250
- NVD CVE-2025-33250
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.