CVE-2024-0095 is a log injection flaw in NVIDIA Triton Inference Server for Linux and Windows. The NVD record scores it 9.0 Critical, while NVIDIA rates it Medium at 4.3. Both are covered below. NVIDIA lists versions 20.10 through 24.04 as affected and 24.05 as the fix.
What's affected
The NVIDIA bulletin (answer 5546) lists Triton Inference Server on Linux and Windows, versions 20.10 to 24.04, as affected. Version 24.05 is the fixed release.
Severity conflict. The NVD record shows CVSS 9.0 Critical. NVIDIA's bulletin shows 4.3 Medium. The bulletin itself is inconsistent: the vector text it displays differs from the one its calculator link uses, and the 4.3 score matches the calculator vector. We report both and suggest you plan around the higher figure until the two sources agree, since the NVD description mentions code execution and escalation of privileges as possible outcomes.
How to check if you're exposed
Triton usually runs as a container, so the quickest check is the image tag.
docker images --format "{{.Repository}}:{{.Tag}}" | grep tritonserver
NVIDIA tags Triton images by release (for example 24.04-py3). Anything from 20.10 up to 24.04 is in the affected range. If you build from source or run a bare metal install, check the version your build reports and your deployment manifests. In Kubernetes, search your manifests and Helm values for the image reference.
What to do now
- Find every Triton deployment, including development and staging clusters, and list the image tags in use.
- Move to Triton 24.05 or later and redeploy.
- Limit who can reach the server endpoints and the logging path. Do not expose inference or management ports to untrusted networks.
- Review how logs are consumed. Any tool that parses or acts on log lines should treat them as untrusted input.
- Confirm the new version is running and record it.
Why it matters
The weakness is CWE-117, improper output neutralization for logs. When an application writes caller supplied text into a log without neutralising it, the writer of that text can add what looks like a genuine entry. NVIDIA describes the possible results as code execution, denial of service, escalation of privileges, information disclosure and data tampering.
The gap between 9.0 and 4.3 usually comes from different assumptions about privileges and scope in the vector. That is why it helps to look at where Triton sits in your own network rather than at the number alone. The record does not flag this CVE as exploited in the wild. Safeguard has a free in-browser dependency scan at gold.safeguard.sh/scan, and the Gold directory lists the CVE and CWE pages used here.
Try it yourself
Click through it at your own pace, or open it full screen.
Quick check
Which score should I use?
Plan for the NVD record score of 9.0 until you have confirmed your exposure, and note NVIDIA rates it 4.3. Where your Triton endpoint is reachable decides how much that gap matters.
Which version fixes it?
NVIDIA lists Triton 24.05 as the fixed release.
Sources
Last reviewed: 19 October 2026.
