Arbitrary file overwrite via rename destination traversal
Published Oct 13, 2026 · Updated Oct 13, 2026
Path traversal in NVIDIA AIStore 4.9 and earlier allows remote attackers to overwrite files via crafted object rename requests. On Linux, the target-side object rename handler fails to confine the supplied destination pathname to its restricted directory, enabling arbitrary file creation or overwrite. Exploitation requires direct network access to an AIStore target but no authentication; the established consequence is unauthorized filesystem modification.
Summary
What happened
Path traversal in NVIDIA AIStore 4.9 and earlier allows remote attackers to overwrite files via crafted object rename requests. On Linux, the target-side object rename handler fails to confine the supplied destination pathname to its restricted directory, enabling arbitrary file creation or overwrite. Exploitation requires direct network access to an AIStore target but no authentication; the established consequence is unauthorized filesystem modification.
The record
- CVE
- CVE-2026-65103
- Published
- Oct 13, 2026
- Updated
- Oct 13, 2026
- Vendor
- NVIDIA
- Product
- AIStore
- Classifications
- CWE-22, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 13, 2026CVE publishedPublication date reported by the CVE source.
- Oct 13, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 to 4.9
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started