SardinhaNews

CVE-2026-102895

CriticalKEV + EUVD🔍 Nuclei

Published: 11/04/2026 · Modified: 11/10/2026

CVSS 3.1ⓘ9.8
EPSSⓘ0.5%
VPR (Tenable)ⓘ—

Description

GPUStack is an open-source GPU cluster manager for AI model serving and GPU instance provisioning. Prior to 2.2.0, get_current_user in gpustack/api/auth.py treated a loopback request source as the built-in administrator when force_auth_localhost was false, which was the default. A remote request could appear to originate from 127.0.0.1 because client_ip_getter accepted a same-host reverse proxy peer or a client-supplied X-GPUStack-Real-IP loopback value. The bypass allowed unauthenticated administrative access, including user and model changes, persistent administrator API-key creation, disclosure of worker and cloud-provider secrets, and code execution through POST /v2/inference-backends/from-yaml. Exploitation was observed in the wild against a 2.1.1 deployment. This issue is fixed in version 2.2.0.

Exploitation

Requires: network access · Does not require: authentication, user interaction, special target conditions

How it is exploited

Exploitation method

  • The attacker sends a remote request to the GPUStack service that can appear to originate from 127.0.0.1 because client_ip_getter accepts a same-host reverse proxy peer or a client-supplied loopback value in the X-GPUStack-Real-IP header.
  • The get_current_user function in gpustack/api/auth.py treats the loopback request as the built-in administrator when force_auth_localhost is false (default).
  • The attacker gains unauthenticated administrative access and can change users and models, create persistent administrator API keys, disclose worker and cloud-provider secrets, and execute code via POST /v2/inference-backends/from-yaml.

Am I affected? (applicability)

  • The GPUStack version in use is prior to 2.2.0.
  • The force_auth_localhost setting is false (default).
  • The GPUStack service is exposed to the network and reachable by remote attackers.
  • A reverse proxy on the same host can forward requests with an apparent loopback origin, or the attacker can send the X-GPUStack-Real-IP header with a loopback value.

Does not require: authentication, user interaction, special target conditions.

Mitigation and detection

  • Update to version 2.2.0 or later.
  • Set force_auth_localhost to true to require authentication even for loopback requests.
  • Restrict network access to the GPUStack service to trusted clients only.
  • Monitor requests with the X-GPUStack-Real-IP header containing loopback values and unauthenticated administrative access.

Impact if exploited

Unauthenticated administrative access — modification of users and models, persistent creation of administrator API keys, disclosure of worker and cloud-provider secrets, and code execution.

Confidentiality: highIntegrity: highAvailability: high

Community reports (unverified): exploitation 2

References and technical detail

The “Requires/Does not require” line and the confidentiality, integrity and availability impact come from the official CVSS vector. Method, applicability and mitigation are an automatic summary of the NVD description, public exploitation sources (Metasploit, Nuclei, Exploit-DB) and the CVE record via CIRCL (advisories and fixed version), linked under “References and technical detail”. Community reports come from CIRCL sightings and are unverified.

Exploitation probability (EPSS) over time

11/06/202611/11/202611/12/2026

Affected products

  • gpustack · gpustack

Weakness type (CWE)

In the news

Timeline on SardinhaNews

References