Cyber Resilience

CVE-2025-33241

Deserialization in Nvidia Nemo ≤ 2.6.1

Published
18 February 2026
Modified
20 February 2026
Patch / advisory
CVSS Score v3.1 7.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0022 12th percentile
Risk Priority 56 floored blend · peak EPSS

Summary

CVE-2025-33241 is a high-severity Deserialization of Untrusted Data (CWE-502) vulnerability in Nvidia Nemo. Its CVSS base score is 7.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 12th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-33241 is a vulnerability in the NVIDIA NeMo Framework that enables an attacker to cause remote code execution by loading a maliciously crafted file. Published on 2026-02-18T14:16:02.927, it carries a CVSS v3.1 base score of 7.8 (High), with vector AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, and is linked to CWE-502 (Deserialization of Untrusted Data). Successful exploitation might result in code execution, escalation of privileges, information disclosure, and data tampering.

The vulnerability can be exploited by a local attacker who has low privileges and requires only low-complexity actions with no user interaction. Upon successful exploitation, the attacker can achieve high impacts to confidentiality, integrity, and availability, potentially leading to the described outcomes of code execution, privilege escalation, information disclosure, and data tampering within the affected system's scope.

Advisories providing details on mitigations and patches are available from NVIDIA at https://nvidia.custhelp.com/app/answers/detail/a_id/5762, the National Vulnerability Database at https://nvd.nist.gov/vuln/detail/CVE-2025-33241, and CVE.org at https://www.cve.org/CVERecord?id=CVE-2025-33241.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

NVIDIA NeMo Framework contains a vulnerability where an attacker could cause remote code execution by loading a maliciously crafted file. A successful exploit of this vulnerability might lead to code execution, escalation of privileges, information disclosure, and data tampering.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-33252Same product: Nvidia Nemo
CVE-2026-24228Same product: Nvidia Nemo
CVE-2025-33245Same product: Nvidia Nemo
CVE-2025-33243Same product: Nvidia Nemo
CVE-2025-33226Same product: Nvidia Nemo
CVE-2025-33253Same product: Nvidia Nemo
CVE-2026-24157Same product: Nvidia Nemo
CVE-2025-33212Same product: Nvidia Nemo
CVE-2026-24159Same product: Nvidia Nemo
CVE-2025-33246Same product: Nvidia Nemo

Affected Assets

nvidia
nemo
≤ 2.6.1

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can uncover deserialization flaws before deployment.

Input validation directly stops deserialization of untrusted data by ensuring inputs are valid before processing.

Engineering principles such as safe deserialization and input sanitization structurally prevent the weakness from being introduced.

Integrity verification tools can detect malformed or tampered serialized data after the fact.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-02 none match
prevents

PR.PS-02 addresses only post-deployment updates/patching and cannot prevent introduction of unsafe deserialization code, yet it can remediate some instances when the flaw exists in outdated libraries or components.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing includes validation of deserialization routines and the use of untrusted data, reducing the likelihood that unsafe object reconstruction will be deployed.

prevents

Requiring vetted libraries, regular updates and SAST before release reduces the likelihood that deserialization logic will accept and act on attacker-controlled serialized objects.

finds

Regular scanning of third-party libraries and timely patching reduce the likelihood that unsafe deserialization vulnerabilities remain active.

none

Mandatory malware scanning of data received over networks or storage media intercepts malicious serialized payloads before they are deserialized by the target application.

References