CVE-2025-23251 json
NVIDIA NeMo Framework contains a vulnerability where a user could cause an improper control of generation of code by remote code execution.
published 2025-04-22 18 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-12280
- cvss
- 7.6
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 53%
- public exploits
- 0
- none known
Summary
NVIDIA NeMo Framework contains a vulnerability where a user could cause an improper control of generation of code by remote code execution. A successful exploit of this vulnerability might lead to code execution and data tampering.
Patch / fix
- nvidia nemo 25.02
- nvidia nemo_framework 25.02
- nvidia nvidia_nemo_framework 25.02
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 18 mo ago
Exploit prediction
0.70% chance of exploitation in the next 30 days, higher than 53% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.6 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:L |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/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/5641
vendor-advisory
Sources
- CVE List CVE-2025-23251
- NVD CVE-2025-23251
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.