CVE-2025-23249
Published: 22 April 2025
Summary
CVE-2025-23249 is a high-severity Deserialization of Untrusted Data (CWE-502) vulnerability in Nvidia Nemo. Its CVSS base score is 7.6 (High).
Operationally, ranked in the top 25.0% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis
NVIDIA NeMo Framework is affected by CVE-2025-23249, a deserialization of untrusted data flaw tracked under CWE-502. The vulnerability allows a remote attacker to trigger unsafe deserialization that results in code execution and data tampering. It carries a CVSS 3.1 base score of 7.6 with the vector AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:L.
An unauthenticated attacker can exploit the issue over the network with low attack complexity and no privileges required, provided a user performs a specific interaction such as loading a crafted artifact. Successful exploitation can yield arbitrary code execution along with modification or corruption of data processed by the framework.
The official NVIDIA advisory is published at https://nvidia.custhelp.com/app/answers/detail/a_id/5641. The current EPSS score of 0.0083 with a recorded peak of 0.0142 reflects limited observed exploitation interest to date.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-12279
Vulnerability details
NVIDIA NeMo Framework contains a vulnerability where a user could cause a deserialization of untrusted data by remote code execution. A successful exploit of this vulnerability might lead to code execution and data tampering.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Penetration testing supplies malicious serialized objects, detecting unsafe deserialization and supporting corrective actions.
Evaluation of untrusted data handling (deserialization testing) reveals unsafe processing, which the required remediation process addresses.
Untrusted serialized data can be deserialized and observed inside the chamber, blocking gadget-chain exploitation outside the sandbox.
Validates or rejects untrusted serialized data before deserialization occurs.
Identifies and blocks malicious code introduced through deserialization of untrusted data at system boundaries.
Integrity verification of serialized information can detect tampering before deserialization occurs.
Provenance of associated data allows detection of untrusted sources before deserialization or processing occurs.