# CVE-2026-24220: Deserialization in TensorRT-LLM

> An attacker can achieve code execution via unsafe deserialization in the visual gen server of NVIDIA TensorRT-LLM.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jul 2026
- **Updated:** 15 Jul 2026
- **Also known as:** GHSA-6f54-qhg5-fhhf

## What is CVE-2026-24220?

CVE-2026-24220 is a medium-severity unsafe deserialization vulnerability in NVIDIA TensorRT-LLM, published on 14 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

NVIDIA TensorRT-LLM for any platform contains a vulnerability in visual gen server, where an attacker could cause an unsafe deserialization by unauthorized zeroMQ deserialization. A successful exploit of this vulnerability might lead to code execution.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2026-24220?

It affects 1 product.


Products: Nvidia Tensorrt-Llm.

## How do I fix CVE-2026-24220?

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

## Is CVE-2026-24220 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-24220 and fix it if it is affected.

What it is: CVE-2026-24220 is a medium-severity unsafe deserialization vulnerability in NVIDIA TensorRT-LLM, published on 14 Jul 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-2026-24220 in the wild and no public exploit code.

Affected product: NVIDIA TensorRT-LLM. 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-2026-24220/ (Markdown: https://insights.sbomify.com/CVE-2026-24220/index.md)
```

## Sources

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

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