/

CVE-2026-47627

Severity:

CRITICAL RISK

(9.8)

Path Traversal (CWE-22) in NVIDIA Triton Inference Server

CVE-2026-47627

Analyzed

Vulnerability type

Category:

Path Traversal

CWE:

CWE-22

Impact:

Denial of Service

Severity:

CRITICAL RISK

(9.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

NVIDIA Triton Inference Server for Linux contains a path traversal vulnerability that may allow an attacker to access or manipulate unintended filesystem paths. A successful exploit could disrupt server availability and cause a denial-of-service condition when vulnerable path handling is reachable.

Affected context

The vulnerability affects NVIDIA Triton Inference Server deployments running on Linux where attacker-controlled path data reaches a filesystem operation without adequate restriction. Risk depends on the exposed server interface, the privileges of the service process, and the filesystem resources available to that process.

Exploit preconditions

  • Attack surface: A reachable Triton Inference Server interface or request-processing path that handles filesystem locations
  • Required access: Ability to submit or influence requests containing path-related input; the exact access requirement depends on deployment configuration
  • Trigger point: Processing of attacker-controlled path data by a filesystem operation
  • Why exploitation is possible: Insufficient canonicalization or containment checks may allow requested paths to escape their intended directory and affect unexpected resources

Why this happens

The underlying bug is improper limitation of a user-influenced pathname. When path values are combined with trusted directories without reliably normalizing the result and enforcing directory containment, traversal elements can redirect filesystem access outside the intended location. This behavior maps to CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal').

Potential impact

  • The service could become unavailable or unstable
  • An attacker may cause denial of service by affecting files or resources used by the server
  • Sensitive filesystem locations could potentially be exposed, depending on process permissions and the affected operation
  • Other workloads on the host could be affected if the service has broad filesystem access

General mitigation guidance

Mitigation generally focuses on reducing trust in request-provided paths and enforcing filesystem boundaries before any access occurs.

Common defensive patterns include:

  • Resolve and canonicalize paths before use, then verify they remain within an approved directory
  • Prefer identifier-based resource selection over accepting arbitrary filesystem paths
  • Apply strict allowlists for permitted files, directories, and path formats
  • Run the inference server with the minimum filesystem and operating-system privileges required
  • Isolate model and temporary-data directories from sensitive host resources
  • Enforce network access controls so administrative or internal interfaces are not broadly exposed

How teams detect issues like this

Organizations can assess for path traversal risks through:

  • Static analysis rules that identify user-controlled values reaching filesystem APIs
  • Code review checks for missing canonicalization, containment validation, or path allowlists
  • Dynamic testing with traversal-oriented input variations in authorized environments
  • Runtime monitoring for unusual file access, repeated malformed requests, and unexpected service failures
  • Policy enforcement that restricts service filesystem permissions and network exposure

Automated security review tools may help identify unsafe path construction and missing boundary checks.

Sources

SourceLink
github.comgithub.com/NVIDIA/product-security/tree/main/2026/5865
nvd.nist.govnvd.nist.gov/vuln/detail/CVE-2026-47627
cve.orgcve.org/CVERecord?id=CVE-2026-47627

Frequently asked

questions

It may be remotely exploitable when a vulnerable Triton interface is network-reachable and accepts attacker-influenced path data. Exploitability depends on deployment exposure and request authorization controls.

Not necessarily. The required access depends on whether the affected request path is exposed anonymously or protected by authentication and authorization.

Constrain all path-derived operations to approved directories using canonicalization, strict containment checks, and allowlists. Limiting the server's filesystem privileges provides additional protection.

Treat request-provided paths as untrusted, prefer logical resource identifiers, test path-boundary enforcement, and monitor filesystem access for anomalous behavior.

Find out what's already
exploitable in your codebase.