GPUStack at a glance
CISA added GPUStack's authentication bypass, CVE-2026-102895 (CVSS 9.8), to its Known Exploited Vulnerabilities catalog on November 9, 2026, after attackers used it against a real deployment. Versions before 2.2.0 can hand unauthenticated attackers full admin access; the fix shipped in 2.2.0 on June 18, 2026.
GPUStack: status
- Affected
- GPUStack before 2.2.0 with force_auth_localhost off (the default), especially behind a same-host reverse proxy
- CVE identifiers
- Resolved on
What changed with GPUStack
CISA added CVE-2026-102895 to its Known Exploited Vulnerabilities catalog on November 9, 2026, with a remediation deadline of November 12 for federal agencies, and GPUStack published its security advisory on the authentication bypass the same day. The flaw sits in GPUStack, an open-source GPU cluster manager used to run AI models across GPU servers. In versions before 2.2.0, the software treated any request that appeared to come from the machine itself (127.0.0.1) as the built-in administrator when the force_auth_localhost setting was off — which was the default.
That shortcut is dangerous in the standard self-hosted setup, where a reverse proxy on the same machine forwards every visitor's request from 127.0.0.1, and a forged X-GPUStack-Real-IP header works too. Either path gives an unauthenticated attacker full administrative access: changing users and models, minting persistent admin API keys, reading worker and cloud-provider secrets, and executing code on worker hosts through custom inference backends. GPUStack says the flaw was exploited in the wild against a deployment running version 2.1.1, where attackers created backends that ran reverse shells. The CVE record, published November 4, scores it 9.8 out of 10 (critical).
Unusually, the fix predates the warning: GPUStack 2.2.0 removed the loopback shortcut and was released on June 18, 2026, months before the CVE record appeared — so any deployment that stayed on 2.1.x is exposed despite a patch being available all along. CISA's listing also flags the flaw for forensic triage, a sign defenders should check reachable servers for signs of compromise, not just patch them.
How to fix it: GPUStack
1. Update
Upgrade GPUStack to 2.2.0 or later and recreate the container; the loopback auto-admin shortcut is removed.
github.com (opens in a new tab)2. Configuration
On older versions, set force_auth_localhost=true so loopback requests also require authentication.
github.com (opens in a new tab)3. Configuration
Strip client-supplied X-GPUStack-Real-IP headers at your reverse proxy.
github.com (opens in a new tab)
Advisories
Why GPUStack matters for businesses
Why it matters: if your agency or your clients self-host open models on GPUStack, this is a same-week fix: upgrade to 2.2.0 or later and recreate the container, or, on older versions, turn on force_auth_localhost and strip the X-GPUStack-Real-IP header at your proxy. Because the bug hands out persistent admin keys and can expose secrets, rotate credentials after upgrading if a server was reachable from the internet.
Get AI News by email
Verified AI stories, each with its official source, on Monday and Thursday mornings. Add breaking news to hear about the biggest ones as soon as we publish them.
Every story links its official source
Free, in English or Spanish
Unsubscribe with one click, any time
Sources for this story
- GPUStack: Authentication bypass via trusted loopback source grants unauthenticated admin (GHSA-gj9m-f8ph-pmhr) (opens in a new tab)Official
GitHub Security Advisories · github.com
- CVE-2026-102895: GPUStack Improper Authentication Vulnerability (opens in a new tab)Official
CISA Known Exploited Vulnerabilities Catalog · cisa.gov
Last verified: . IA Compa summarizes public announcements for business readers. We are not affiliated with the companies mentioned. Always confirm details, pricing, and availability with the official source.
- #gpustack
- #cve-2026-102895
- #authentication-bypass
- #cisa-kev
- #gpu-cluster
- #self-hosted
- #security