CVE-2026-24208
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedNVIDIA Triton Inference Server contains a vulnerability where an attacker could cause a path traversal issue. A successful exploit of this vulnerability might lead to denial of service.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceNVIDIA Triton Inference Server contains a path traversal vulnerability that allows attackers to access files outside the intended directory boundaries through specially crafted file paths. This could enable denial of service by causing the server to read or access unexpected system resources.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 26.03CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Triton Inference Server installationRun 'tritonserver --version' or check for the tritonserver binary in common paths like /opt/tritonserver/bin/, /usr/local/bin/, or via 'which tritonserver'. Also check running processes with 'ps aux | grep tritonserver'.Affected if Triton Inference Server is installed and running.
-
Determine installed versionRun 'tritonserver --version 2>&1' to get the exact version number. Compare this version against the affected range (< 26.03).Affected if The installed version is earlier than 26.03.
-
Check if HTTP/REST or gRPC endpoint is exposedReview the Triton server startup command or config file for flags like '--http-port', '--grpc-port', '--allow-http', '--allow-grpc'. Check if port 8000 (HTTP) or 8001 (gRPC) is listening with 'netstat -tlnp | grep -E "800[01]"' or 'ss -tlnp | grep -E "800[01]"'.Affected if HTTP or gRPC endpoints are enabled and accessible (this is the default configuration).
-
Verify if model repository contains untrusted filesExamine the model repository directory (specified via '--model-repository' flag) to confirm whether it only contains expected model files. Check for any unusual files or symbolic links pointing outside the intended directory structure.Affected if The model repository contains user-uploaded files or is accessible to untrusted users.
-
Inspect HTTP request handling logsReview Triton server logs (typically stderr/stdout or configured log files) for any requests containing '../' or directory traversal patterns in URI paths. Use 'grep -r "\.\./" /var/log/triton/ 2>/dev/null' or similar pattern matching on logs.Affected if Log entries show directory traversal sequences in requests (indicates active exploitation attempts or testing).
If Triton Inference Server version is below 26.03 AND HTTP/gRPC endpoints are exposed, the environment is vulnerable to path traversal attacks via specially crafted file path requests.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped26.03
Implement strict input validation and canonicalization of file paths to ensure all file access requests stay within intended boundaries. Restrict file system permissions and consider adding request size/length limits.
26.03 or later
- Stop the running Triton Inference Server instance
- Backup current configuration, models, and any custom data
- Download Triton Inference Server version 26.03 or later from NVIDIA's official distribution channels (NGC or GitHub releases)
- Install the new version following NVIDIA's standard deployment procedures
- Verify the installation by checking the Triton Inference Server version
- Restart the Triton Inference Server service
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-24208 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-24208 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data