CVE-2026-102895: GPUStack Improper Authentication Vulnerability

The CVE record, as listed on ThreatInt, rates CVE-2026-102895 CRITICAL: 9.8[2]. It says the record was Published 2026-11-04[2].According to the CVE description reproduced by VulDB, before version 2.2.0, GPUStack's authentication code treated a loopback request source as the built-in administrator when force_auth_localhost was false, which was the default[3].The GitLab Advisory Database says that when GPUStack runs behind a same-host reverse proxy, every remote request arrives at GPUStack with TCP peer 127.0.0.1, so the loopback auto-admin branch fires[4]. It also says a forged X-GPUStack-Real-IP: 127.0.0.1 header can cause the request source to be treated as loopback[4].The CVE record says the bypass allowed persistent administrator API-key creation, disclosure of worker and cloud-provider secrets, and code execution[2]. It adds that exploitation was observed in the wild against a 2.1.1 deployment[2].According to SecurityOnline, researcher Javier Sixto of ulex.fr reported active attacks in the wild[1].Ostorlab reports that GPUStack 2.2.0 is released with the fix[5] on June 18, 2026. It says the upgrade closes the bypass but leaves existing users and API keys in place[5], and it advises users to revoke unknown administrator keys and rotate the worker and cloud credentials[5].Ostorlab said the flaw was not in the CISA Known Exploited Vulnerabilities catalog as of November 5, 2026[5]. A later automated GitHub alert lists it In CISA KEV: Yes[6], with a KEV remediation due date: 2026-11-12[6].