CVE-2026-24173
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 server crash by sending a malformed request to the server. 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 fails to properly handle malformed requests, allowing an attacker to trigger a server crash through specially crafted input. This represents a denial-of-service vulnerability in the request parsing/handling path.
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.02CVSS 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 versionRun 'tritonserver --version' or check the container image tag/Dockerfile for the installed version of NVIDIA Triton Inference ServerAffected if The installed version is below 26.02 (e.g., 25.x, 24.x, etc.)
-
Confirm server is network accessibleVerify that Triton Inference Server is configured to listen on a network interface (0.0.0.0 or specific IP) rather than only localhost, check the --http-address or --grpc-address configuration flagsAffected if The server accepts network requests from untrusted sources or is exposed to the internet
-
Verify request endpoints are exposedCheck if HTTP or gRPC endpoints are enabled (--http-port, --grpc-port flags) and accessible to clients for model inference requestsAffected if Inference endpoints are enabled and reachable by potential attackers
-
Inspect logging for crash eventsReview Triton server logs for unexpected process exits, segfaults, or abnormal termination that may correlate with malformed request handlingAffected if The server exhibits unexpected crashes or instability under certain input conditions
You are affected if Triton Inference Server version is below 26.02 AND the server is exposed to network requests that could contain malformed input from untrusted clients.
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.02
Implement robust input validation and error handling on all request endpoints to prevent crash conditions from malformed requests. Consider adding request schema validation and bounds checking before processing.
26.02 or later
- 1. Identify the current installed version of NVIDIA Triton Inference Server
- 2. Stop the Triton Inference Server service
- 3. Download and install Triton Inference Server version 26.02 or later from NVIDIA's official repositories
- 4. Verify the installed version matches the fixed release
- 5. 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-24173 — 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-24173 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