dbcve.org
Triton Inference ServerApplication · Nvidia

CVE-2026-24213

CRITICAL · 9.8 CVSS v3.1 Published 2026-05-20
Fix available
A fix is available. Upgrade to 26.03 or later.
See remediation →
100/100
Remediation priority · Urgent
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 in the DALI backend where an attacker could cause an out-of-bounds read. A successful exploit of this vulnerability might lead to code execution, data tampering, denial of service, or information disclosure.

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 out-of-bounds read vulnerability in its DALI (Data Loading Library) backend. An attacker could exploit this to read memory beyond allocated buffers, potentially leading to code execution, data tampering, denial of service, or information disclosure. The CVSS 9.8 score indicates the vulnerability is network-exploitable and requires no authentication.

MitigationApply the NVIDIA-provided patch or update to a fixed version of Triton Inference Server. If immediate patching is not possible, consider network segmentation and restricting access to the inference server endpoints.

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:< 26.03

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

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

  1. Identify Triton Inference Server version
    Query the server's metrics or health endpoint (e.g., GET /v2/health/ready), or check the installed package/container image tag. Run 'tritonserver --version' if CLI is available, or inspect the running container: 'docker ps --format "{{.Image}}"'
    Affected if The installed version is below 26.03 (e.g., 26.02, 26.01, older) or cannot be determined to be 26.03 or higher
  2. Confirm DALI backend is in use
    Inspect model configuration files (config.pbtxt) for any model using the DALI backend. Look for 'backend: dali' or 'execution_accelerators' with DALI specified in the model repository. Check Triton logs for DALI initialization messages.
    Affected if Any model is configured to use the DALI backend (dali execution accelerator)
  3. Check model repository for DALI configurations
    Search the model repository for files containing 'dali' or 'DALI' in config.pbtxt files. Run: 'grep -r "dali" /path/to/model/repository/*.pbtxt'
    Affected if DALI is explicitly configured in any model's config.pbtxt
  4. Assess network exposure of Triton server
    Review firewall rules, network policies, or service mesh configuration to determine if Triton Inference Server is accessible from untrusted networks. Check if the server binds to 0.0.0.0 or an exposed interface.
    Affected if The Triton server is reachable from network segments without authentication (the CVE states attacker needs to interact with DALI processing pipeline)

User is affected if Triton Inference Server version is below 26.03 AND the DALI backend is actively used in any model configuration, particularly if the server is network-accessible.

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 26.03 or later
Fixed in 26.03
Interim mitigation

Apply the NVIDIA-provided patch or update to a fixed version of Triton Inference Server. If immediate patching is not possible, consider network segmentation and restricting access to the inference server endpoints.

Recommended fix Moderate confidence

Triton Inference Server 26.03

  1. 1. Identify the currently installed Triton Inference Server version using `tritonserver --version` or checking the container image tag
  2. 2. Backup any custom configurations, models, and data directories before upgrading
  3. 3. Pull the updated Triton Inference Server container image with tag 26.03 or later (e.g., `docker pull nvcr.io/nvidia/tritonserver:26.03-py3`)
  4. 4. Stop the currently running Triton Inference Server container gracefully
  5. 5. Update deployment scripts or Kubernetes manifests to reference the new image version
  6. 6. Start the upgraded Triton Inference Server container with the same configuration parameters
  7. 7. Verify the server starts successfully and loads expected models
  8. 8. Test inference endpoints to confirm normal operation
Caveat No specific breaking changes documented for this security patch; minor version within same release train typically compatible

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

Fix this in Triton Inference Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,480
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,568.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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