NVIDIA AIStore Critical Flaw Lets Attackers Revoke Tokens Without Auth

NVIDIA AIStore for Linux contains a critical security vulnerability that allows unauthenticated remote attackers to compromise system integrity. According to the National Vulnerability Database record for CVE-2026-65173, the issue stems from a missing authentication control in a specific endpoint. This flaw enables attackers to submit crafted token-revocation lists without proper verification. The vulnerability is rated 9.1 on the Common Vulnerability Scoring System, placing it in the critical severity category.

The technical root of the problem is classified under CWE-306, which denotes missing authentication for critical functionality. In this scenario, the token-revocation endpoint fails to verify the identity of the requester. An attacker can send maliciously crafted lists to this endpoint from any remote location. Because no authentication is required, the system processes these requests as if they were legitimate administrative actions. This bypasses standard security controls designed to protect sensitive operations.

Technical Impact Analysis

The consequences of exploiting this vulnerability include data tampering and denial of service. By submitting crafted revocation lists, an attacker can invalidate legitimate tokens used by authorized users or services. This action disrupts normal operations and can prevent valid users from accessing the storage system. The National Vulnerability Database notes that a successful exploit may lead to these specific outcomes. The ability to revoke tokens at will undermines the trust model of the AIStore framework.

Affected Components and Versions

This vulnerability affects the NVIDIA AIStore framework for Linux. Specifically, all versions from 0 up to and including 4.9 are impacted. The National Vulnerability Database record lists the affected range as "0 to 4.9". This means any deployment using these versions of the framework is potentially vulnerable to the unauthenticated token-revocation attack. Organizations running these versions should assume their systems are exposed until further notice.

Defender's checklist

Administrators should verify the version of NVIDIA AIStore currently running on their Linux systems. Check if the version falls within the 0 to 4.9 range identified in the CVE record. Monitor network traffic for unusual activity targeting the token-revocation endpoint. Look for signs of unauthorized token invalidation or unexpected service disruptions. Document any anomalies for further investigation and potential incident response.

Background: Incident response plans

An incident response plan is a documented procedure for detecting, containing, and recovering from security breaches. It defines roles, communication channels, and technical steps to minimize damage, preserve evidence, and restore normal operations quickly.

Read the full guide: Incident Response Plans: Why Your Security Tools Fail Without One

What to do and how to stay safe: NVIDIA

• Identify all systems running NVIDIA AIStore for Linux and check their version numbers against the affected range of 0 to 4.9.
• Implement network-level access controls to restrict access to the token-revocation endpoint to trusted internal networks only.
• Monitor logs for unexpected token revocation events or spikes in authentication failures that may indicate exploitation attempts.
• Prepare to apply updates once the vendor provides a patch or mitigation guidance for CVE-2026-65173.

Step-by-step guide: Patch Management vs Vulnerability Management: The Critical Distinction

General security guidance from the InfoSec Ledger newsroom. It is not confirmed advice from the organisations named in this story.

Frequently asked questions

What is the CVSS score for CVE-2026-65173?

The vulnerability has a CVSS score of 9.1, which is rated as critical severity.

Which versions of NVIDIA AIStore are affected?

All versions of the NVIDIA AIStore framework for Linux from 0 to 4.9 are affected.

Can an attacker exploit this without credentials?

Yes, the vulnerability allows an unauthenticated remote attacker to submit crafted token-revocation lists.