dbcve.org
CWE-288Weakness · CWE-288

CVE-2026-47481

MEDIUM · 6.5 CVSS v3.1 Published 2026-07-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 6 weeks old

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 Linux contains a vulnerability where an attacker can cause an authentication bypass through an alternative path or channel. A successful exploit of this vulnerability might lead to code execution, escalation of privileges, information disclosure, and data tampering.

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 for Linux contains an authentication bypass vulnerability where an attacker can circumvent authentication mechanisms through an alternative path or channel. This allows unauthenticated access to functionality that should require authentication, potentially enabling code execution, privilege escalation, information disclosure, or data tampering.

MitigationReview all API endpoints and code paths in Triton Inference Server to ensure authentication is consistently enforced. Apply vendor-supplied patches when available and verify that all service endpoints require valid authentication.

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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

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 running
    Run 'ps aux | grep tritonserver' or check if port 8000/8001/8002 (default Triton ports) are listening using 'netstat -tlnp | grep -E "800[0-9]"'
    Affected if Triton Inference Server process is found running on the system
  2. Determine the installed Triton version
    If Triton is running, check the version via the Docker container tag, installed package version, or query the server metadata endpoint at http://localhost:8000/v2 - note that version information may be visible in server logs or via 'tritonserver --version' if CLI is available
    Affected if The installed version is older than the patched version released by NVIDIA for this CVE (compare against vendor advisory)
  3. Verify authentication configuration settings
    Examine the Triton configuration file (typically in /etc/triton or config.pbtx) for 'auth' or 'authorization' settings. Check if 'allow-unauthenticated' or similar flags are set to true, or review YAML/config files for authentication backend settings.
    Affected if Authentication is explicitly disabled, set to false, or 'allow-unauthenticated' is enabled in the configuration
  4. Test API endpoints for unauthenticated access
    Attempt to access Triton endpoints without credentials: curl http://localhost:8000/v2/models, curl http://localhost:8000/v2/health/ready, curl http://localhost:8000/v2/infer. Also test inference endpoints that should require auth.
    Affected if Any sensitive endpoint returns successful data or accepts requests without returning 401/403 authentication errors
  5. Review network exposure of Triton services
    Check if Triton ports (8000-8002) are bound to 0.0.0.0 or an exposed network interface using 'netstat -tlnp' or 'ss -tlnp'. Verify firewall rules allow external access to these ports.
    Affected if Triton services are accessible from untrusted networks without authentication being required

The environment is affected if Triton Inference Server is running with authentication disabled, misconfigured, or bypassed, or if sensitive endpoints are accessible without credentials.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Review all API endpoints and code paths in Triton Inference Server to ensure authentication is consistently enforced. Apply vendor-supplied patches when available and verify that all service endpoints require valid authentication.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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