High Insecure deserialization

CVE-2025-33226 — Deserialization of Untrusted Data in NVIDIA Nemo

NVIDIA NeMo Framework for all platforms contains a vulnerability where malicious data created by an attacker may cause a code injection. A successful exploit of this vulnerability may lead to code execution, escalation of privileges, information disclosure, and data tampering.

Published Dec 16, 2025 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: nvidia

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.2% (30-day exploitation probability)+2
Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.22%

ahead of 12% of scored CVEs · Oct 14, 2026

Affects

NVIDIA

Nemo and 1 more

CVSS base

7.8

High · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

None

none · proof-of-concept · active

Automatable

can an attacker script the kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (NVIDIA Nemo, NVIDIA NeMo Framework).
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes matching the vulnerability class (insecure deserialization), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
NVIDIA	Nemo	< 2.5.3	Vulnerable	NIST National Vulnerability Database
NVIDIA	NeMo Framework	version All versions prior to 2.5.3	Vulnerable	CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Local

Attack complexity

Low

Privileges required

Low

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
7.8	CVSS 3.1	High	1.8	5.9	psirt@nvidia.com via NIST National Vulnerability Database
7.8	CVSS 3.1	High	—	—	nvidia via CVE Program (cve.org) e CISA ADP

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: psirt@nvidia.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-502 · Deserialization of Untrusted Data

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.22%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Monitor serialized objects in requests and unexpected processes spawned by the runtime.

endpoint telemetry (EDR)application logs

Timeline

What happened to this CVE, newest first.

2026
Affected products added · nvidia/nemo framework
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
SSVC assessment updated
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 13, 2026
CVSS changed · 7.8
Oct 13, 2026 · NIST National Vulnerability Database
Source status changed · → Analyzed
Oct 13, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 13, 2026 · NIST National Vulnerability Database
2025
CVE published
Dec 16, 2025 · nvidia

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

3 on the record

nvidia.custhelp.com/app/answers/detail/a_id/5736
Vendor Advisory, NIST National Vulnerability Database
www.cve.org/CVERecord
Technical Description, NIST National Vulnerability Database
nvd.nist.gov/vuln/detail/CVE-2025-33226
Technical Description, NIST National Vulnerability Database

Elsewhere on this site

NVIDIA
every CVE for this vendor

Insecure deserialization
same class

CWE-502
other pages naming this weakness

Related CVEs (same products)

High CVE-2026-24252 OS Command Injection in NVIDIA Nemo Jul 27, 2026
High CVE-2026-24228 Deserialization of Untrusted Data in NVIDIA Nemo Jun 16, 2026
High CVE-2026-24155 Code Injection in NVIDIA Nemo Jun 16, 2026
Critical CVE-2026-24159 Deserialization of Untrusted Data in NVIDIA Nemo Mar 24, 2026
Critical CVE-2026-24157 Deserialization of Untrusted Data in NVIDIA Nemo Mar 24, 2026
High CVE-2025-33253 Deserialization of Untrusted Data in NVIDIA Nemo Feb 18, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No fixed version, patch or mitigation documented.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2025-33226 is "Deserialization of Untrusted Data in NVIDIA Nemo", rated High. It affects Nemo (NVIDIA); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.8 describes technical severity. EPSS 0.22% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.