CVE-2026-102895: GPUStack Auth Bypass and Admin Code Execution

CVE-2026-102895 is an authentication bypass in GPUStack before 2.2.0 where the get_current_user function treats any request from 127.0.0.1 as the built-in administrator by default. A remote attacker can manipulate the X-GPUStack-Real-IP header or exploit a reverse proxy to make a request appear from localhost, gaining unauthorized admin access without credentials. The impact includes creation of persistent admin API keys, modification of users and models, access to worker and cloud provider secrets, and remote code execution via POST /v2/inference-backends/from-yaml.

The vulnerability has a CVSS score of 9.8 (critical). Official NVD data published on 2026-11-04 confirms exploitation in the wild against GPUStack 2.1.1 deployments. Social media posts within the last 24 hours report the CVE as critical with specific focus on loopback authentication bypass. Severity is consistent across all available sources. No publicly declared GitHub repositories containing exploit code have been identified, limiting public availability of exploitation details.

For defenders (sysadmins, CISOs, IT teams): upgrade to GPUStack 2.2.0 with maximum priority. Before upgrading, audit access logs for POST requests to /v2/inference-backends/from-yaml and /v2/admin from localhost (127.0.0.1) over recent weeks, searching for exploitation patterns. Immediately rotate all administrator API keys and cloud provider secrets. Verify integrity of AI models and GPU worker configuration.

GPUStack is frequently deployed in AI research environments, startups, and tech companies where GPU instances are managed centrally. The authentication bypass is particularly critical in these contexts because it allows an attacker to steal cloud integration secrets (AWS, Azure, GCP), compromise training models, and gain persistent access to the infrastructure. The lack of authentication for administrative operations eliminates the first layer of defense.

The patch is available in GPUStack 2.2.0. The developer fixed the issue by modifying client_ip_getter logic and preventing acceptance of client-supplied loopback headers, requiring proper verification of the source address. Check the official GPUStack changelog to confirm version 2.2.0 is available in your environment and apply the update according to your urgent maintenance window.