gpustack
Affected
- introduced
0.7.1, fixed2.2.2(ecosystem)
Fixed versions
2.2.2
Fix
- Fixed version
2.2.2pip install --upgrade gpustack==2.2.2
Advisory
Also known as: CVE-2026-102894
GPUStack: SAML callback trusts an unverified SAMLResponse, allowing authentication bypass and account takeover
Impact
The callback Base64-decodes the posted XML, reads NameID and attributes, resolves or provisions the user, and mints a gpustack_session JWT — but never calls OneLogin_Saml2_Auth.process_response(), the step that verifies the signature, issuer, audience, destination, and time conditions.
No credentials are required, and SAML SSO does not even need to be configured. The callback processes the payload and issues a session regardless of whether SAML is set up, so every deployment is affected, not only SAML-enabled ones. Anyone who can reach the endpoint over the network can authenticate as an arbitrary identity by posting a response that names it:
Administrator access grants full control over the deployment and the infrastructure it manages. Because Response/Assertion IDs are never consumed, a captured signed response also replays indefinitely.
Precondition: network reachability to /auth/saml/callback. SAML SSO configuration is not required. A full proof-of-concept is available privately to maintainers.
Patches
Fixed in gpustack 2.2.2:
Workarounds
There is no effective configuration-level workaround — disabling or not configuring SAML does not mitigate this on affected versions, since the callback runs regardless. Until upgraded, block network access to /auth/saml/callback (e.g. at a reverse proxy / ingress).
Credit
Reported privately by Austin Chu, Sohee Kim, and Corban Villa (UC Berkeley
security research project), and independently, earlier, by a researcher who wishes to remain anonymous.
Critical Basis: The source's own band: CRITICAL
0.7.1, fixed 2.2.2 (ecosystem)2.2.2
2.2.2pip install --upgrade gpustack==2.2.2Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0