CVE-2026-47487
Triton Inference Server vulnerability analysis and mitigation

Overview

CVE-2026-47487 is a path traversal vulnerability (CWE-22) in NVIDIA Triton Inference Server for Linux that allows a local, low-privileged user to read, write to, or modify files outside the intended model repository by supplying a crafted path in the model name field to the Triton MLflow plugin. It affects all versions of NVIDIA Triton Inference Server up to and including version 26.02 on Linux. The vulnerability was disclosed on August 4, 2026, with NVD initial analysis completed on August 17, 2026. NVD assigns a CVSS v3.1 base score of 7.1 (High), while NVIDIA's own CNA scoring rates it 4.4 (Medium) (GitHub Advisory, NVIDIA Advisory).

Technical details

The root cause is improper neutralization of path traversal sequences (CWE-22) in the Triton MLflow plugin's handling of the model name parameter. When a user submits a model name containing directory traversal sequences (e.g., ../../), the plugin fails to restrict the resulting file path to the designated model repository directory, allowing file system operations to reach arbitrary locations on the host. Exploitation requires local access and low-level privileges, with no user interaction needed. No public proof-of-concept code has been identified at this time (GitHub Advisory, NVIDIA Advisory).

Impact

Successful exploitation allows a local attacker to read sensitive files outside the model repository (high confidentiality impact per NVD scoring), potentially exposing credentials, configuration files, or proprietary model data. The attacker may also write to or modify arbitrary files accessible to the Triton service account, which could disrupt service availability and constitute a denial of service condition. Integrity impact is assessed as none by both NVD and NVIDIA's CNA, though file modification capability is noted in the description (GitHub Advisory, NVIDIA Advisory).

Exploitability

There is no evidence of active in-the-wild exploitation or publicly available proof-of-concept code as of the time of disclosure. CISA's SSVC assessment classifies exploitation as "none" and the attack as non-automatable with partial technical impact. The EPSS score is approximately 0.163–0.184%, placing it in the 8th percentile for exploitation likelihood within 30 days. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog (GitHub Advisory, NVIDIA Advisory).

Exploitation steps

  1. Gain local access: Obtain a low-privileged local account on a Linux system running NVIDIA Triton Inference Server with the MLflow plugin enabled (versions up to and including 26.02).
  2. Identify the MLflow plugin endpoint: Locate the Triton server's model management API or MLflow plugin interface, typically accessible via the Triton HTTP/gRPC API.
  3. Craft a malicious model name: Construct a model name containing path traversal sequences such as ../../etc/passwd or ../../sensitive/config to reference files outside the model repository.
  4. Submit the request: Send a request to the Triton MLflow plugin using the crafted model name, triggering the plugin to perform file read, write, or modification operations on the targeted path.
  5. Retrieve or manipulate target files: Depending on the operation triggered, read sensitive files (e.g., credentials, configuration) or overwrite files to cause denial of service or further privilege escalation (GitHub Advisory, NVIDIA Advisory).

Indicators of compromise

  • Logs: Triton Inference Server access logs showing model name parameters containing ../ or URL-encoded equivalents (%2e%2e%2f) in MLflow plugin requests; file access errors or unexpected file paths in server logs.
  • File System: Unexpected access timestamps on sensitive files outside the model repository (e.g., /etc/, /home/, application config directories) coinciding with Triton service activity; new or modified files in directories not associated with model storage.
  • Process: Triton server process accessing file paths outside the designated model repository directory as observed via auditd or inotifywait monitoring tools.

Mitigation and workarounds

NVIDIA has released a patch addressing this vulnerability; users should update NVIDIA Triton Inference Server to a version beyond 26.02 as referenced in the August 2026 security bulletin. As interim mitigations, administrators should restrict file system permissions on the model repository and surrounding directories to limit the scope of files accessible by the Triton service account. Additionally, consider restricting or disabling the MLflow plugin in sensitive environments until patching is complete, and enforce least-privilege principles for accounts with access to the Triton server (NVIDIA Advisory, GitHub Advisory).

Additional resources


SourceThis report was generated using AI

Related Triton Inference Server vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-47627CRITICAL9.8
  • Triton Inference Server logoTriton Inference Server
  • cpe:2.3:a:nvidia:triton_inference_server
NoNoAug 18, 2026
CVE-2026-47629HIGH7.5
  • Triton Inference Server logoTriton Inference Server
  • cpe:2.3:a:nvidia:triton_inference_server
NoNoAug 18, 2026
CVE-2026-47628HIGH7.5
  • Triton Inference Server logoTriton Inference Server
  • cpe:2.3:a:nvidia:triton_inference_server
NoNoAug 18, 2026
CVE-2026-47606MEDIUM6.5
  • Triton Inference Server logoTriton Inference Server
  • cpe:2.3:a:nvidia:triton_inference_server
NoNoAug 18, 2026
CVE-2026-47630MEDIUM5.5
  • Triton Inference Server logoTriton Inference Server
  • cpe:2.3:a:nvidia:triton_inference_server
NoNoAug 18, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management