High severity · published Feb 18, 2026
CVE-2025-33253
NVIDIA NeMo Framework contains a vulnerability where an attacker could cause remote code execution by convincing a user to load a maliciously crafted file
7.3
CVSS
0.2%
EPSS
No
On KEV
Description
NVIDIA NeMo Framework contains a vulnerability where an attacker could cause remote code execution by convincing a user to load a maliciously crafted file. A successful exploit of this vulnerability might lead to code execution, denial of service, information disclosure, and data tampering.
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
Required
Confidentiality
High
Integrity
High
Availability
High
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.2% · higher than 13% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
NE
Nemo · Nvidia
before 2.6.1 · source: NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2025-33253
CVE.org
https://www.cve.org/CVERecord?id=CVE-2025-33253
US Government Resource
https://nvd.nist.gov/vuln/detail/CVE-2025-33253
Vendor Advisory
https://nvidia.custhelp.com/app/answers/detail/a_id/5762
Third Party Advisory
https://www.cve.org/CVERecord?id=CVE-2025-33253
More from Nemo
9.8
CVE-2026-24159
NVIDIA NeMo Framework contains a vulnerability where an attacker may cause remote code execution
9.8
CVE-2026-24157
NVIDIA NeMo Framework contains a vulnerability in checkpoint loading where an attacker could cause remote code execution
9.8
CVE-2025-23304
NVIDIA NeMo library for all platforms contains a vulnerability in the model loading component, where an attacker could cause code injection by loading .nemo files with maliciously…
9.8
CVE-2025-23303
NVIDIA NeMo Framework for all platforms contains a vulnerability where a user could cause a deserialization of untrusted data by remote code execution
9.8
CVE-2025-23251
NVIDIA NeMo Framework contains a vulnerability where a user could cause an improper control of generation of code by remote code execution