CVE-2025-23311
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 stack overflow through specially crafted HTTP requests. A successful exploit of this vulnerability might lead to remote code execution, denial of service, information disclosure, or data tampering.
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 stack overflow vulnerability in its HTTP request handling path. An unauthenticated remote attacker can send specially crafted HTTP requests to trigger the overflow, potentially achieving remote code execution, denial of service, information disclosure, or data manipulation.
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< 25.07CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 if NVIDIA Triton Inference Server is deployedCheck running processes for 'tritonserver' or list installed packages using package manager (e.g., 'dpkg -l | grep tritonserver' or 'pip list | grep triton'). Also check for Docker containers named 'triton' or 'tritonserver'.Affected if Triton Inference Server is installed and running
-
Determine the installed Triton Inference Server versionRun 'tritonserver --version' if the binary is available, or check the container image tag/digest if running via Docker. Compare against the affected version range: versions prior to 25.07 are vulnerable.Affected if Installed version is older than 25.07 or version cannot be determined
-
Verify network exposure of Triton HTTP endpointsCheck if Triton server ports (default HTTP: 8000, gRPC: 8001, metrics: 8002) are listening on externally accessible network interfaces using 'netstat -tlnp' or 'ss -tlnp'. Inspect firewall rules and container port mappings.Affected if HTTP endpoints are reachable from untrusted network segments
-
Inspect HTTP request handling configurationReview Triton configuration files or environment variables for HTTP server settings. Check if request size limits or input validation is configured via 'tritonserver --http-service-src-size' or similar flags.Affected if No request size limits or input validation is configured for HTTP endpoints
-
Check for signs of exploitation attemptsReview Triton server logs for异常HTTP请求 patterns, stack overflow errors, or service instability. Look for warnings containing 'overflow', 'buffer', 'crash', or malformed request indicators.Affected if Logs show stack overflow errors or suspicious malformed HTTP requests
User is affected if Triton Inference Server is exposed over HTTP and the installed version is prior to 25.07
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 · scoped25.07
Apply the NVIDIA-provided patch or upgrade to a patched version of Triton Inference Server. Network exposure should be minimized and the inference server should not be directly internet-facing.
Triton Inference Server 25.07 or later
- Download Triton Inference Server version 25.07 or later from the official NVIDIA repository
- Stop the currently running Triton Inference Server instance
- Install the updated Triton Inference Server version 25.07 or newer
- Restart the Triton Inference Server service
- Verify the server is running the updated version using the server's health check or version endpoint
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-23311 — 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-2025-23311 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