CVE-2025-23325
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 uncontrolled recursion through a specially crafted input. 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 contains a vulnerability where specially crafted input can trigger uncontrolled recursion, likely causing a stack overflow or infinite loop condition that leads to denial of service.
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.05CVSS 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 if Triton Inference Server is presentCheck for running Triton processes: 'ps aux | grep tritonserver' or check for Triton installation directories like '/opt/tritonserver' or container images containing 'tritonserver'Affected if Triton Inference Server is found in the environment
-
Determine the installed Triton versionRun 'tritonserver --version' or check the version from the container image tag, installation directory, or packaging system (e.g., 'dpkg -l | grep triton' or 'pip show triton-inference-server')Affected if Unable to determine version or version string shows a number less than 25.05
-
Compare against affected version rangeIf version is obtained, verify it is less than 25.05 (e.g., 25.04, 24.x, earlier). Note that version 25.05 and later contain the fix.Affected if Installed version is any release prior to 25.05
If NVIDIA Triton Inference Server is installed and the version is below 25.05, the environment is affected by this uncontrolled recursion vulnerability.
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.05
Apply the latest NVIDIA Triton Inference Server security patch or upgrade to a patched version once available.
25.05
- 1. Identify the current Triton Inference Server version by running 'tritonserver --version' or checking the Docker image tag
- 2. Back up all configuration files, model repositories, and any custom settings
- 3. Stop the Triton Inference Server service
- 4. Upgrade to Triton Inference Server version 25.05 or later
- 5. For Docker deployments: pull the new image (e.g., 'docker pull nvcr.io/nvidia/tritonserver:25.05-py3' or the appropriate tag)
- 6. For native installations: follow NVIDIA's installation guide for version 25.05 using apt, yum, or pip as appropriate
- 7. Restore configuration files and model repository paths
- 8. Start the Triton Inference Server service
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-23325 — 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-23325 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