Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach AIStore dSort endpoint over network
-
DeliverySubmit dSort job with crafted archive
-
ExploitTraversal sequences in member names bypass directory restriction
-
ExecutionWrite/overwrite files outside target directory
-
PersistAchieve code execution or data tampering
-
ImpactInformation disclosure or denial of service
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Path canonicalization, traversal prevention
MITRE ATT&CK
2 techniques across 2 tactics: Discovery, Collection The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the attacker to be able to submit a dSort (distributed sort) job to the AIStore cluster and supply a crafted archive (e.g., tar/zip) whose member names embed path traversal sequences that the dSort extraction component fails to sanitize. The practical prerequisite and primary limiting factor is network access to the AIStore dSort/API endpoint: although CVSS marks PR:N (no authentication), in typical deployments the dSort job-submission interface is reachable only from within a trusted ML/training cluster or private network, so internet-facing exposure is the main risk amplifier. The AC:H rating indicates that reliably crafting the malicious archive and triggering the flaw is non-trivial; no user interaction is required (UI:N). |
| Impact | This is a credible, elevated-priority vulnerability but not a drop-everything emergency based on current signals. The vendor-assigned CVSS 3.1 vector (CVSS:3.1/AV:N/AC:H/PR:N/UI:N) scores 8.1 and indicates a network-reachable, unauthenticated flaw (PR:N) with high attack complexity (AC:H) and high impact across confidentiality, integrity, and availability - consistent with a path traversal (CWE-22) that can lead to arbitrary file write and downstream code execution. No EPSS score was provided in the input, so exploitation probability cannot be quantified. There is no CISA KEV listing and no public proof-of-concept in the provided data, so this is best treated as 'no public exploit identified at time of analysis' rather than active exploitation. No SSVC decision data was supplied. The key tension to verify: PR:N implies no authentication, yet exploitation requires the ability to submit a dSort job to the AIStore cluster, which in many real deployments is restricted to internal/trusted clients on a private network - the real-world attack surface therefore depends heavily on whether the AIStore API/dSort endpoint is network-exposed to untrusted actors. The AC:H rating also signals that crafting a working exploit is non-trivial. Net: a genuine high-severity issue warranting prompt patching, especially where AIStore is reachable beyond a trusted ML cluster boundary, but the AC:H rating and absence of KEV/POC/EPSS signals argue against treating it as an imminently weaponized threat. |
| Exploit ScenarioDerived | An attacker with network reach to an NVIDIA AIStore cluster submits a dSort job referencing a crafted archive whose member entries contain path traversal sequences (e.g., ../../). During extraction, dSort fails to constrain the output pathname, writing attacker-controlled files outside the intended directory and overwriting sensitive files or planting executable content, potentially leading to code execution, data tampering, information disclosure, or denial of service. No public proof-of-concept is identified in the provided data, and the vendor's AC:H rating indicates a non-trivial crafting effort. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 13, 2026
Path traversal in the NVIDIA AIStore for Linux dSort archive extraction component allows a remote attacker to write files outside the intended extraction directory by submitting a dSort job that references an archive (e.g., tar/zip) whose member names contain crafted traversal sequences, yielding arbitrary file creation or overwrite and potentially code execution, information disclosure, data tampering, and denial of service. The vulnerability carries a CVSS 3.1 base score of 8.1 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H) per the assessed vector, indicating remote reachability and no authentication requirement, but a high attack-complexity rating that reflects the difficulty of reliably crafting the malicious archive and triggering the flaw. There is no confirmed active exploitation (CISA KEV) and no public exploit code identified at time of analysis; the practical gating factor is network access to the AIStore dSort/API endpoint, which in typical deployments is confined to a trusted ML/training cluster or private network rather than being internet-facing. Because the dSort job-submission path is the attack surface, exposure is primarily amplified where AIStore's API is reachable from untrusted networks, and no user interaction is required.
RemediationAI
No vendor-released patch or exact fix version is identified in the provided data, so remediation should begin by consulting the NVIDIA product security advisory at https://github.com/NVIDIA/product-security/tree/main/2026/5889 (also referenced via https://nvd.nist.gov/vuln/detail/CVE-2026-65164 and https://www.cve.org/CVERecord?id=CVE-2026-65164) to obtain the patched release and upgrade guidance; apply the vendor-published update as soon as a fixed build is confirmed, as that is the only definitive remedy for the traversal flaw. Until a patch is available and deployed, the highest-value compensating control is network containment: restrict the AIStore API and dSort job-submission endpoints to trusted ML/training cluster networks via firewall rules, security groups, or mTLS-ingress so untrusted clients cannot submit dSort jobs at all - this eliminates the attack path but breaks any legitimate external job orchestration that depends on remote dSort access. If dSort functionality is not required, disable or deny dSort job creation entirely; the trade-off is loss of distributed sort capability for datasets. Where dSort must remain enabled, restrict job creation to authenticated, tightly scoped service accounts and run the AIStore process under a least-privilege user with its working and extraction directories confined to a dedicated volume or container so traversal writes cannot reach sensitive paths or executables - this reduces but does not eliminate impact. Additional hardening includes validating archive member names before extraction (rejecting entries containing '..', absolute paths, or symlink targets that escape the extraction root), ensuring the extraction destination is a canonicalized path with containment checks, and monitoring for dSort jobs referencing archives with traversal sequences or for unexpected file creation outside configured data directories, which can provide early detection of exploitation attempts.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is a classic CWE-22 improper limitation of a pathname to a restricted directory ('path traversal') rooted in the dSort (distributed sort) archive extraction routine of NVIDIA AIStore, a distributed object storage system designed for AI/ML workloads. When a dSort job is created, AIStore can extract archives (tar, zip, and similar containers) to process their contents; the extraction logic fails to normalize and confine member names, so entries containing sequences such as '../' or absolute paths escape the target directory. Because the affected code performs filesystem writes on behalf of the storage cluster, a traversal write lands with the privileges of the AIStore process, enabling arbitrary file creation or overwrite. The CVSS vector AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H describes a network-reachable, unauthenticated-per-vector issue whose high attack complexity stems from the need to construct a valid archive that survives parsing while carrying malicious member names, with an unchanged scope but high confidentiality, integrity, and availability impact. The root cause is the absence of canonicalization and containment enforcement (resolving to an absolute path and verifying it remains within the extraction root) before writing each archive member to disk. No CPE strings were supplied in the available intelligence feed, so exact affected version ranges cannot be enumerated from the input data; affected deployments are those running NVIDIA AIStore for Linux that expose or permit dSort job creation and archive extraction.
Know when Nvidia gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
dSort job submission is network-reachable without authentication (AV:N/PR:N), crafting a reliable traversal archive is non-trivial (AC:H), and file write enables full CIA impact (C:H/I:H/A:H).
Primary rating from Vendor (nvidia).
CVSS VectorVendor: nvidia
DescriptionCVE.org
NVIDIA AIStore for Linux contains a path traversal vulnerability in the dSort archive extraction component where a remote attacker may cause an improper limitation of a pathname to a restricted directory by supplying crafted archive member names to a dSort job. A successful exploit may lead to arbitrary file creation or overwrite, code execution, information disclosure, data tampering, and denial of service.
Articles & Coverage 2
Executive ViewAI
NVIDIA AIStore for Linux dSort archive extraction is affected by a high-severity path traversal vulnerability that could allow an unauthenticated remote attacker to write files outside the intended extraction directory, potentially enabling code execution, data tampering, information disclosure, or denial of service. Because the dSort/API endpoint is often confined to trusted ML/training networks, exposure depends on network segmentation, but a successful exploit could disrupt AI data pipelines and corrupt stored datasets. Leadership should treat this as a high-impact data integrity and availability risk until a vendor patch is available.
Restrict dSort/API endpoint access to trusted networks; disable dSort archive extraction if not required; run dSort workers as low-privileged accounts in containers with read-only root filesystems and no write access outside designated extraction directories; validate and canonicalize archive member names to reject traversal sequences, absolute paths, and symlinks; use WAF/reverse-proxy rules to block traversal patterns in dSort job submissions; monitor and alert on unexpected file creation or overwrite outside extraction paths; apply vendor patch when released.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
Heap-based buffer overflow in dnsmasq before 2.78 allows remote attackers to cause a denial of service (crash) or execut
Systems with microprocessors utilizing speculative execution and speculative execution of memory reads before the addres
The NVIDIA driver in the Graphics Drivers subsystem in Apple OS X before 10.11.4 allows attackers to execute arbitrary c
The NVIDIA driver before 307.78, and Release 310 before 311.00, in the NVIDIA Display Driver service on Windows does not
NVIDIA Windows GPU Display Driver (all versions) contains a vulnerability in DirectX drivers, in which a specially craft
Authentication bypass in NVIDIA Triton Inference Server allows unauthenticated remote attackers to reach protected funct
NVIDIA Windows GPU Display Driver (all versions) contains a vulnerability in DirectX drivers, in which a specially craft
NVIDIA Container Toolkit for Linux contains a Time-of-Check Time-of-Use (TOCTOU) vulnerability when used with default co
For the NVIDIA Quadro, NVS, and GeForce products, NVIDIA GeForce Experience R340 before GFE 2.11.4.125 and R375 before G
The native Bluetooth stack in the Linux Kernel (BlueZ), starting at the Linux kernel version 2.6.32 and up to and includ
The NVIDIA Graphics Drivers subsystem in Apple OS X before 10.11.5 allows attackers to execute arbitrary code in a privi
NVIDIA Container Toolkit 1.16.1 or earlier contains a Time-of-check Time-of-Use (TOCTOU) vulnerability when used with de
EUVD-2026-98559
GHSA-rp48-97jq-3x4r
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB