Security readout for executives and security teams
Plain-English summary
A remotely reachable flaw in NVIDIA Triton Inference Server for Linux could let an unauthenticated attacker traverse file paths. Successful exploitation may disrupt inference services through denial of service. The supplied CVSS assessment is 9.8, making exposed deployments an urgent review priority.
Executive priority
Treat internet-facing or broadly reachable Triton deployments as immediate priorities. Identify affected systems, reduce exposure, and follow NVIDIA remediation guidance. Internal, tightly restricted deployments still require timely review because exploitation requires no privileges or user interaction according to the CVSS vector.
Technical view
CVE-2026-47627 is a CWE-22 path-traversal vulnerability affecting the listed Triton Inference Server range 0.0–26.05. Its CVSS 3.1 vector indicates network access, low complexity, no privileges, and no user interaction. The description confirms potential denial of service; it does not explain how the scored confidentiality and integrity impacts occur.
Likely exposure
Linux systems running the listed Triton Inference Server range may be affected. Risk is greatest where the service is reachable from untrusted networks. The bundle does not identify vulnerable interfaces, required configuration, deployment patterns, or a confirmed fixed version.
Exploitation context
The CVSS vector describes unauthenticated remote exploitation with low complexity and no user interaction. However, the bundle contains no evidence of public exploitation or active attacks, and the CVE is not listed as KEV. Exploit maturity remains unknown.
Researcher notes
The supplied description confirms path traversal and possible denial of service only. Although the CVSS vector scores confidentiality, integrity, and availability as high, the bundle provides no technical mechanism supporting those broader impacts. Patch details, vulnerable components, prerequisites, and proof-of-concept status are not included.
Mitigation direction
- Inventory Triton Inference Server versions and identify systems within the listed affected range.
- Restrict Triton access to trusted networks and authenticated administrative paths where operationally feasible.
- Review NVIDIA advisory 5865 for confirmed fixed versions or vendor-approved mitigations.
- Apply the vendor-confirmed remediation after testing service compatibility and inference workloads.
- Increase monitoring for unexpected file-access errors, crashes, restarts, or inference-service availability failures.
Validation and detection
- Record installed Triton versions, Linux hosts, deployment owners, and network exposure.
- Confirm whether untrusted clients can reach each Triton service without crossing approved access controls.
- Review service and platform logs for abnormal path errors, crashes, restarts, or availability incidents.
- Verify the deployed version against NVIDIA advisory 5865 after remediation.
- Reassess network exposure and service health without attempting exploit reproduction in production.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-47627 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9nvidiaVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://nvd.nist.gov/vuln/detail/CVE-2026-47627CVE reference, nvidia
- https://www.cve.org/CVERecord?id=CVE-2026-47627CVE reference, nvidia
- https://github.com/NVIDIA/product-security/tree/main/2026/5865CVE reference, nvidia
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Limitation of a Pathname to a Restricted Directory
Improper Limitation of a Pathname to a Restricted Directory represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.