CVE-2024-0087 is a Critical (CVSS 9.0) flaw in NVIDIA Triton Inference Server for Linux, where a user can set the logging location to an arbitrary file and logs are appended to it if it exists. Versions 22.09 through 24.03 are affected. Upgrade to 24.04 or later and restrict the logging API.
What's affected
- Product: NVIDIA Triton Inference Server for Linux.
- Affected versions: 22.09 through 24.03, per the NVIDIA bulletin. The record's CPE entry is a wildcard and does not narrow this.
- Fixed version: 24.04.
- Severity: Critical, CVSS 9.0, network vector, low complexity, no user interaction, high privileges required, changed scope. The record and the bulletin agree.
- NVIDIA's mitigation: upgrade to 24.04 or later, follow the Secure Deployment Considerations Guide, and make sure logging APIs are restricted to authorized users.
- Exploitation: the record's KEV flag is false, and the bulletin does not report exploitation.
How to check if you're exposed
Find every Triton deployment. If you run it from NVIDIA containers, the image tag usually carries the release, such as 24.03. List running images:
docker images | grep -i tritonserver
On Kubernetes, check the image fields in your Triton deployments. Then compare each release to the range 22.09 through 24.03.
Also check who can reach the server's logging API. The bulletin points to restricting logging APIs to authorized users, so look at network policy, any gateway in front of Triton, and whether the endpoint is open beyond the inference clients that need it.
What to do now
- List all Triton Inference Server deployments and their release versions.
- Upgrade anything from 22.09 through 24.03 to 24.04 or later.
- Restrict access to the logging and management APIs to authorized users only.
- Read NVIDIA's Secure Deployment Considerations Guide and compare your deployment with it.
- Run the server as a low privilege user so that file writes reach as little as possible. This is general hardening, not a bulletin step.
Why it matters
The record maps this to CWE-73 (CWE-73), external control of file name or path. When a caller can choose where a service writes, the service becomes a way to append data to files it should never touch. NVIDIA lists code execution, denial of service, privilege escalation, information disclosure and data tampering as possible outcomes.
The high privilege requirement narrows who can trigger it, but inference servers often sit behind shared credentials, and a changed scope means damage can spread past Triton itself. Reachability matters here: a Triton instance with no exposed logging API is in a much better place than one open to a whole network. Upgrading removes the question.
Try it yourself
Click through it at your own pace, or open it full screen.
Quick check
Which Triton version fixes CVE-2024-0087?
24.04. Versions 22.09 through 24.03 are affected according to the NVIDIA bulletin.
Is there a mitigation besides upgrading?
NVIDIA recommends following its Secure Deployment Considerations Guide and keeping logging APIs restricted to authorized users. It still recommends upgrading.
Sources
- NVIDIA security bulletin 5535 (Triton Inference Server, May 2024)
- Safeguard Gold entry for CVE-2024-0087
Last reviewed: 19 October 2026.
