GPUStack auth bypass grants unauthenticated admin (GHSA-gj9m-f8ph-pmhr)
First seen Nov 9 Updated Nov 10, 17:18 UTC Heat 40 high evidence
A GitHub advisory says GPUStack before v2.2.0 treats requests from a loopback source as the built-in administrator when force_auth_localhost is False, the default. Behind a same-host reverse proxy, all remote requests appear as 127.0.0.1, so no credentials are needed. The X-GPUStack-Real-IP header can also trigger this.
- What to do
- Upgrade gpustack to 2.2.0.
- Who should care
- Operators of self-hosted GPUStack, especially behind a local reverse proxy.
Why it matters: GPUStack before 2.2.0 behind a same-host reverse proxy gives every remote request admin rights, so upgrading to 2.2.0 is required.
Key facts
- Affected
- gpustack (pip) < 2.2.0
- Patched
- 2.2.0
- CVSS
- 9
Context
This appears to be the same flaw class as the actively exploited GPUStack authentication issue in T5, though the items do not confirm the link.
Timeline
Official
Evidence
High evidence: the claim comes from an official source (the company or project itself), or at least two independent sites reported it.
Details written Nov 10, 16:10 UTC from the sources listed above.