Skip to content
NewA calmer, faster ZeroHour

CVE-2026-102895

Authentication bypass in GPUStack before 2.2.0

CISA: GPUStack Improper Authentication Vulnerability

CVSS 3.1
9.8 critical
EPSS
<1%p47
Published
·
Added to KEV
Analyze CVE-2026-102895 with Vani AIImpact, affected versions, exploitation status, mitigations and detection

GPUStack prior to 2.2.0 contains an authentication bypass in gpustack/api/auth.py that treats loopback requests as administrator by default. An unauthenticated remote attacker can trigger it by sending a request with X-GPUStack-Real-IP set to a loopback value or via a same-host reverse proxy. This grants full admin access including user/model changes, persistent admin API keys, worker/secret disclosure, and code execution via POST /v2/inference-backends/from-yaml. Affected are all prior deployments; fixed in 2.2.0.

What to do: Upgrade to GPUStack 2.2.0. No workaround available.

ProductAffectedFixed in
GPUStackprior to 2.2.02.2.0
Estimated exposure
No basis for an estimate.

Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.

Description · NVD

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.

KEVCISA Known Exploited Vulnerability
Affected
GPUStack GPUStack
Required action
Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
Due date
Ransomware use
Unknown
Vendors
gpustack
Products
gpustack
Ecosystems
pip
Weakness
CWE-287, CWE-290, CWE-346
Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
GHSA
GHSA-gj9m-f8ph-pmhr (critical)

In the news

5 stories