# CVE-2026-16497: Denial of service in Triton Inference Server

> An attacker can cause excessive iteration in NVIDIA Triton Inference Server, leading to a denial of service.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Sep 2026
- **Updated:** 8 Sep 2026
- **Also known as:** GHSA-rmxr-g66j-gfhg

## What is CVE-2026-16497?

CVE-2026-16497 is a high-severity denial of service vulnerability in NVIDIA Triton Inference Server, published on 8 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

NVIDIA Triton Inference Server for Linux contains a vulnerability where an attacker could cause excessive iteration. A successful exploit of this vulnerability might lead to denial of service.

Weakness: CWE-834 (Excessive Iteration)

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


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

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

## Is CVE-2026-16497 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-16497 is a high-severity denial of service vulnerability in NVIDIA Triton Inference Server, published on 8 Sep 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-16497 in the wild and no public exploit code.

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

## Sources

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

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