CVE-2026-47477
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 Linux contains a vulnerability where an attacker can cause a stack-based buffer overflow. 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 for Linux contains a stack-based buffer overflow vulnerability where an attacker can overflow a fixed-size stack-allocated buffer, potentially causing the application to crash or behave unpredictably, resulting in denial of service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify Triton Inference Server installationRun 'tritonserver --version' or check for the binary at /opt/tritonserver/bin/tritonserver, then retrieve the version stringAffected if The installed version is present and matches any unpatched release of Triton Inference Server for Linux
-
Verify the service is actively runningCheck process status with 'ps aux | grep tritonserver' or 'systemctl status triton-inference-server'Affected if The Triton Inference Server process is running and accepting network connections
-
Assess network exposureReview configuration files in /etc/tritonserver/ or ~/.tritonserver/ for HTTP/gRPC endpoint bindings, and run 'netstat -tlnp | grep tritonserver' or 'ss -tlnp | grep tritonserver' to identify listening portsAffected if The service listens on accessible network interfaces (0.0.0.0 or external IPs) rather than only localhost
-
Check for oversized payload vectorsExamine inference endpoint configurations (model repository settings, HTTP/gRPC service configs) to identify data ingestion paths that accept client payloadsAffected if Inference endpoints that accept variable-length input data are exposed over the network without documented input length validation
The environment is affected if NVIDIA Triton Inference Server for Linux is running an unpatched version with network-accessible inference endpoints that can receive client payloads capable of triggering the stack buffer overflow.
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 · scopedApply available NVIDIA Triton Inference Server security patches; in the interim, restrict network exposure and implement input length validation on all data ingestion paths to prevent oversized payloads from reaching vulnerable functions.
Latest Triton Inference Server release as specified in NVIDIA's security bulletin for this CVE
- Check the current installed version of NVIDIA Triton Inference Server using the container image tag or `tritonserver --version`
- Review NVIDIA's official security bulletin for CVE-2026-47477 to obtain the specific fixed version number
- Upgrade to the fixed version of Triton Inference Server by pulling the updated container image from NVIDIA NGC or your container registry
- Verify the upgrade by running `tritonserver --version` in the new container to confirm the patched version is installed
- Test your inference workflows to ensure functionality is maintained after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-47477 — 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-2026-47477 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