PatchSiren cyber security CVE debrief
CVE-2026-65173 NVIDIA CVE debrief
AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-10-13T13:00:43.477Z and has not been modified since then. The vulnerability allows an unauthenticated remote attacker to submit crafted token-revocation lists, potentially leading to data tampering and denial of service. Defenders responsible for NVIDIA AIStore framework deployments on Linux, particularly those using versions 0 to 4.9, should assess exposure and prioritize verification and compensating controls.
- Vendor
- NVIDIA
- Product
- AIStore framework
- CVSS
- CRITICAL 9.1
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-10-13
- Original CVE updated
- 2026-10-13
- Advisory published
- 2026-10-13
- Advisory updated
- 2026-10-13
Who should care
Defenders responsible for NVIDIA AIStore framework deployments on Linux, particularly those using versions 0 to 4.9, should assess exposure and prioritize verification and compensating controls.
Why it matters
Defenders should prioritize verifying exposure of AIStore framework versions 0 to 4.9 on Linux and assessing compensating controls due to the missing authentication vulnerability.
- Potential data tampering requires verification and mitigation
- Potential denial of service requires verification and mitigation
- Exposure of AIStore framework versions 0 to 4.9 on Linux requires verification
- Compensating controls may be necessary for affected systems
Technical summary
NVIDIA AIStore for Linux contains a missing authentication vulnerability in the token-revocation endpoint. An unauthenticated remote attacker may submit crafted token-revocation lists, potentially leading to data tampering and denial of service. The vulnerability affects AIStore framework versions 0 to 4.9 on Linux, and defenders should prioritize verifying exposure and assessing compensating controls. The CVE record and NVD entry provide details on the missing authentication vulnerability in NVIDIA AIStore for Linux.
Defensive priority
Defenders should prioritize verifying exposure of AIStore framework versions 0 to 4.9 on Linux and assessing compensating controls.
Recommended defensive actions
- Verify AIStore framework versions 0 to 4.9 on Linux are exposed and assess compensating controls
- Review and update inventory to identify affected systems
- Implement additional authentication measures for token-revocation endpoints
- Monitor for suspicious activity related to crafted token-revocation lists
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
Evidence notes
The CVE record and NVD entry provide details on the missing authentication vulnerability in NVIDIA AIStore for Linux. The vulnerability allows an unauthenticated remote attacker to submit crafted token-revocation lists, potentially leading to data tampering and denial of service.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-65173 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-65173
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-65173 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-65173
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
CVE-2026-65173
Unverified legacy reference
URL: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/65xxx/CVE-2026-65173.json
cve_program_cvelist_v5
-
Source reference
Unverified legacy reference
URL: https://github.com/NVIDIA/product-security/tree/main/2026/5889
Supplemental source
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.