Code execution via unsafe PodSpec security settings
Published Oct 13, 2026 · Updated Oct 13, 2026
Privilege misuse in NVIDIA AIStore 4.9 and earlier allows remote attackers to execute code via legacy ETL PodSpec initialization. The API accepts caller-supplied Kubernetes host-namespace and container-security settings instead of preserving the ETL isolation boundary. Exploitation requires access to this legacy API in a Linux Kubernetes deployment, needs no credentials or user interaction, and also enables privilege escalation, data disclosure, and tampering.
Summary
What happened
Privilege misuse in NVIDIA AIStore 4.9 and earlier allows remote attackers to execute code via legacy ETL PodSpec initialization. The API accepts caller-supplied Kubernetes host-namespace and container-security settings instead of preserving the ETL isolation boundary. Exploitation requires access to this legacy API in a Linux Kubernetes deployment, needs no credentials or user interaction, and also enables privilege escalation, data disclosure, and tampering.
The record
- CVE
- CVE-2026-65162
- Published
- Oct 13, 2026
- Updated
- Oct 13, 2026
- Vendor
- NVIDIA
- Product
- AIStore
- Classifications
- CWE-250, T1611
- 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.
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