dbcve.org
Triton Inference ServerApplication · Nvidia

CVE-2025-33201

HIGH · 7.5 CVSS v3.1 Published 2025-12-03
Fix available
A fix is available. Upgrade to 25.10 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 contains a vulnerability where an attacker may cause an improper check for unusual or exceptional conditions issue by sending extra large payloads. A successful exploit of this vulnerability may 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 improper check for unusual or exceptional conditions vulnerability where sending extra large payloads triggers a denial of service. The software fails to properly validate or handle oversized input data, leading to service disruption.

MitigationImplement input validation controls to enforce payload size limits on Triton Inference Server endpoints. Restrict network access to minimize attack surface until an official patch is available.

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.10

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 Triton Inference Server is installed
    Check for Triton Inference Server processes running (e.g., 'tritonserver' process) or look for installation directories commonly at /opt/tritonserver or /usr/local/tritonserver
    Affected if Triton Inference Server is running or installed on the system
  2. Determine the installed version
    Run 'tritonserver --version' or check the version string in the binary metadata, docker image tag, or installation directory
    Affected if The version number is lower than 25.10 (e.g., 25.09, 25.08, earlier versions)
  3. Verify network exposure of Triton endpoints
    Check if Triton server ports (default 8000 for HTTP/REST, 8001 for gRPC, 8002 for metrics) are listening on external interfaces by reviewing netstat/ss output or firewall rules
    Affected if The Triton Inference Server API endpoints are accessible from untrusted network segments
  4. Inspect existing input validation controls
    Review any proxy, load balancer, or application-layer configuration in front of Triton to see if payload size limits are enforced (e.g., max request body size settings)
    Affected if No payload size limits or input validation controls are configured upstream from Triton

You are affected if Triton Inference Server is running with a version below 25.10 and its endpoints are network-accessible without payload size restrictions.

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.10 or later
Fixed in 25.10
Interim mitigation

Implement input validation controls to enforce payload size limits on Triton Inference Server endpoints. Restrict network access to minimize attack surface until an official patch is available.

Recommended fix High confidence

25.10

  1. Identify the current installed version of Triton Inference Server using `tritonserver --version` or checking the container image tag
  2. Stop any running Triton Inference Server instances
  3. Upgrade Triton Inference Server to version 25.10 or later by pulling the updated container image (e.g., `docker pull nvcr.io/nvidia/tritonserver:25.10-py3` or the appropriate tag for your deployment method)
  4. Verify the upgrade was successful by running `tritonserver --version` or checking the container image
  5. Restart the Triton Inference Server service with the updated version
  6. Monitor the service to ensure it is running correctly

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

Fix this in Triton Inference Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-33201 — 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-33201 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