# CVE-2025-33244: Deserialization in Apex

> An unauthorized attacker can exploit untrusted data deserialization in NVIDIA APEX to execute code, escalate privileges, or tamper with data.

- **Severity:** Critical 9.0 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Mar 2026
- **Updated:** 25 Mar 2026
- **Also known as:** GHSA-x6mp-6wvc-9f66

## What is CVE-2025-33244?

CVE-2025-33244 is a critical unsafe deserialization vulnerability in NVIDIA Apex, published on 24 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

NVIDIA APEX for Linux contains a vulnerability where an unauthorized attacker could cause a deserialization of untrusted data. This vulnerability affects environments that use PyTorch versions earlier than 2.6. A successful exploit of this vulnerability might lead to code execution, denial of service, escalation of privileges, data tampering, and information disclosure.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2025-33244?


## How do I fix CVE-2025-33244?

No fix has been published for CVE-2025-33244 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-33244 being exploited?

There is no known exploitation of CVE-2025-33244 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-33244 and fix it if it is affected.

What it is: CVE-2025-33244 is a critical unsafe deserialization vulnerability in NVIDIA Apex, published on 24 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-33244 in the wild and no public exploit code.

Affected product: NVIDIA Apex. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-33244/ (Markdown: https://insights.sbomify.com/CVE-2025-33244/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-33244
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-33244
- OSV: https://osv.dev/vulnerability/CVE-2025-33244

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-33244/
Summaries are generated and may contain mistakes; the official description above is the record.