dbcve.org
Triton Inference ServerApplication · Nvidia

CVE-2025-23323

HIGH · 7.5 CVSS v3.1 Published 2025-08-06
Fix available
A fix is available. Upgrade to 25.05 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
NVIDIA Triton Inference Server for Windows and Linux contains a vulnerability where a user could cause an integer overflow or wraparound, leading to a segmentation fault, by providing an invalid request. 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 confidence

NVIDIA Triton Inference Server contains an integer overflow or wraparound vulnerability in request processing logic. When a user provides a specially crafted invalid request, the integer overflow can cause memory corruption leading to a segmentation fault, resulting in denial of service.

MitigationApply vendor-provided patches for Triton Inference Server. In the interim, implement input validation and bounds checking on request parameters to reject malformed requests before they reach vulnerable processing logic.

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
Triton Inference ServerApplication
Affected:< 25.05

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if NVIDIA Triton Inference Server is present
    Check for Triton Server binary, container image, or running service. Common paths: /opt/tritonserver, /usr/local/bin/tritonserver, or look for docker containers named 'triton' or 'tritonserver'.
    Affected if Triton Inference Server is installed or running on the system
  2. Determine installed Triton Server version
    Run 'tritonserver --version' or check container image tag. If using the Python server, run 'python -c "import triton_inference_server; print(triton_inference_server.__version__)"'
    Affected if Version is below 25.05 (e.g., 25.04, 25.03, older releases)
  3. Confirm server accepts external requests
    Verify the Triton Server HTTP/REST or gRPC endpoint is exposed and accessible. Check configuration files or running process for --http-port, --grpc-port, or --metrics-port flags.
    Affected if Server has exposed inference endpoints that accept client requests

You are affected if Triton Inference Server is running with a version earlier than 25.05 and accepts inference requests from clients or users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 25.05 or later
Fixed in 25.05
Interim mitigation

Apply vendor-provided patches for Triton Inference Server. In the interim, implement input validation and bounds checking on request parameters to reject malformed requests before they reach vulnerable processing logic.

Recommended fix High confidence

25.05

  1. Verify current Triton Inference Server version using `tritonserver --version` or checking the Docker image tag
  2. For Docker deployments: Pull the fixed image using `docker pull nvcr.io/nvidia/tritonserver:25.05-py3` or later
  3. Stop the current Triton Inference Server instance
  4. Update to version 25.05 or later using your deployment method (Docker, pip, or binary)
  5. For Docker: Run `docker run --gpus=1 --rm -p8000:8000 -p8001:8001 -p8002:8002 nvcr.io/nvidia/tritonserver:25.05-py3 tritonserver --model-repository=/models`
  6. For pip: Run `pip install triton-inference-server==25.05` or later
  7. Verify the new version is running with `tritonserver --version`
  8. Test that inference requests work correctly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Triton Inference Server Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-23323 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-23323 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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