CVE-2026-24209
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 has a path traversal vulnerability that allows an attacker to access files outside the intended directory through specially crafted input. This could enable denial of service by causing the server to read or access unexpected files and 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 'docker ps' or check for Triton processes: 'ps aux | grep triton' or check installed packages. Look for container named 'triton inference server' or binary at /opt/tritonserver/bin/tritonserver'Affected if Triton Inference Server is found running or installed on the system
-
Determine installed versionRun 'tritonserver --version' or for Docker: 'docker exec <container_id> tritonserver --version'. Check the version string against the 26.03 thresholdAffected if The installed version is lower than 26.03 (e.g., 26.02, 25.xx, etc.)
-
Verify network exposure of Triton API endpointsCheck if Triton server ports (typically 8000 for HTTP, 8001 for gRPC, 8002 for metrics) are listening on non-localhost: 'netstat -tlnp | grep -E "8000|8001|8002"' or review Docker port mappingsAffected if Triton API ports are bound to 0.0.0.0 or exposed externally, making the vulnerability remotely exploitable
-
Inspect Triton model repository configurationCheck the model repository path configured in Triton (typically via --model-repository flag or TRITON_MODEL_REPOSITORY env var). Review any configuration files specifying directory paths used by TritonAffected if Model repository points to a shared or writable filesystem location, indicating potential for path traversal impact
-
Check for file path input usage in inference workflowsReview application logs and configuration for use of model inputs that accept file paths, custom ensemble configurations, or Python backend scripts that process file pathsAffected if Inference workflows accept or process user-supplied file paths that could be manipulated via the path traversal flaw
You are affected if Triton Inference Server version is below 26.03 and the server is exposed on the network with file path input capabilities in use.
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 sanitization for all file path inputs, ensuring paths are normalized and validated against an allowed directory whitelist before use.
Triton Inference Server 26.03 or later
- Backup all Triton Inference Server configuration files, models, and data directories
- Stop the currently running Triton Inference Server instance
- Download Triton Inference Server version 26.03 or later from NVIDIA's official repository
- Install the new version following NVIDIA's standard upgrade procedure
- Verify the installation by starting the server and checking that it runs without errors
- Test that path traversal prevention is working correctly by attempting authorized file access operations
- Deploy the updated server to production
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.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 $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-24209 — 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-24209 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