# CVE-2026-24227: Deserialization in TensorRT

> An attacker can execute arbitrary code by exploiting a deserialization vulnerability in NVIDIA TensorRT.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jul 2026
- **Updated:** 15 Jul 2026
- **Also known as:** GHSA-f54h-33c8-78p4

## What is CVE-2026-24227?

CVE-2026-24227 is a medium-severity unsafe deserialization vulnerability in NVIDIA TensorRT, published on 14 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

NVIDIA TensorRT for contains a vulnerability where a user might cause a deserialization of untrusted data. 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-24227?

It affects 1 product.


Products: Nvidia Tensorrt.

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

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

## Is CVE-2026-24227 being exploited?

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

## Other vulnerabilities in NVIDIA TensorRT

- [CVE-2026-24188](https://insights.sbomify.com/CVE-2026-24188/): Memory corruption in TensorRT (high 8.2)
- [CVE-2026-24238](https://insights.sbomify.com/CVE-2026-24238/): Memory corruption in TensorRT (high 7.8)
- [CVE-2026-24268](https://insights.sbomify.com/CVE-2026-24268/): Memory corruption in TensorRT (high 7.8)
- [CVE-2026-24272](https://insights.sbomify.com/CVE-2026-24272/): Memory corruption in TensorRT (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-24227 is a medium-severity unsafe deserialization vulnerability in NVIDIA TensorRT, published on 14 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-24227 in the wild and no public exploit code.

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

## Sources

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

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