CVE-2025-23310
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 for Windows and Linux contains a vulnerability where an attacker could cause stack buffer overflow by specially crafted inputs. A successful exploit of this vulnerability might lead to remote code execution, denial of service, information disclosure, and 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 buffer overflow vulnerability in its input processing path that can be triggered by specially crafted inputs. The overflow allows an attacker to overwrite stack memory, potentially achieving remote code execution with the server's privileges. This affects both Windows and Linux deployments of the inference server.
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 Triton Inference Server installationRun command: `tritonserver --version` or check Docker image tag if running in container: `docker images | grep triton`Affected if Version is present and below 25.07 (e.g., 25.06, 25.05, older releases)
-
Determine if Triton server process is activeRun: `ps aux | grep tritonserver` on Linux or check Services on Windows for Triton Inference ServerAffected if Server process is running and listening on network ports (typically 8000, 8001, 8002)
-
Verify network accessibilityCheck listening ports: `netstat -tlnp | grep -E '8000|8001|8002'` or `ss -tlnp | grep -E '8000|8001|8002'` on Linux; on Windows use `netstat -an | findstr '8000'`Affected if Server ports are bound to 0.0.0.0 or an exposed network interface, allowing remote connections to inference endpoints
-
Confirm input processing endpoints are reachableTest health endpoint: `curl -s http://localhost:8000/v2/health/ping` (adjust port if different) or use wgetAffected if HTTP endpoints respond, confirming the input processing path is active and accessible
-
Check for authentication configurationInspect Triton config.pbtxt or startup flags for `grpc_api_auth` or `http_auth` settings; also check if behind a reverse proxy with authAffected if No authentication is configured and server is network-accessible, meaning untrusted inputs can reach the vulnerable processing path
You are affected if Triton Inference Server version is below 25.07 AND the server is running with accessible network endpoints, allowing untrusted inputs to reach the input processing path.
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 security patch for CVE-2025-23310 immediately to all affected Triton Inference Server deployments. Until patched, restrict network access to the inference server and validate input sources.
Triton Inference Server 25.07
- Identify the current Triton Inference Server version in use
- Stop the Triton Inference Server service
- Upgrade Triton Inference Server to version 25.07 or later using the appropriate package manager or installation method for your platform (Windows or Linux)
- Verify the installation by checking the version number
- Restart the Triton Inference Server service
- Test that inference workflows function correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.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 $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-23310 — 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-23310 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