GPUStack: SAML callback trusts an unverified SAMLResponse, allowing authentication bypass and account takeover
Affects gpustackSource GCVE Database
Not known to be exploited · CVSS 9.1 Critical : upgrade to 2.2.2 as a priority.
Data as of 10 Nov 2026, 17:35 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 9.1 |
|---|
- Patch
- Available – fixed in 2.2.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 4 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.
What to do
Upgrade gpustack to 2.2.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| PyPIgpustack | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade gpustack to version 2.2.2 or later, where the SAML callback properly validates responses using OneLogin_Saml2_Auth.process_response() and restricts callback routes to active configured providers. Until patched, block network access to the /auth/saml/callback endpoint (e.g., via reverse proxy or ingress) as there is no effective configuration-level workaround. Disabling or not configuring SAML does not mitigate the vulnerability in affected versions.
Description
A critical authentication bypass vulnerability exists in gpustack versions from 0.7.1 up to but not including 2.2.2. The SAML callback endpoint processes unverified SAML responses without validating signatures or other security checks, allowing attackers with network access to authenticate as any user, including administrators, or provision new non-admin users. This leads to full account takeover and potential control over the deployment and managed infrastructure. The issue affects all deployments regardless of whether SAML SSO is configured. The vulnerability is fixed in gpustack 2.2.2 by enforcing proper SAML response validation and restricting callback routes to active providers only.
References
- github.com/gpustack/gpustack/security/advisories/GHSA-62m9-f875-rqw6 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-102894 (opens in a new tab)
- github.com/gpustack/gpustack/pull/5753 (opens in a new tab)
- github.com/gpustack/gpustack/pull/5923 (opens in a new tab)
- github.com/gpustack/gpustack/commit/705edbe1b5feec63959306daecd640e1c70eced2 (opens in a new tab)
- github.com/gpustack/gpustack/commit/adc6d82be34e48390720a1361df616e2ea9d6d45 (opens in a new tab)
- github.com/gpustack/gpustack (opens in a new tab)
- github.com/gpustack/gpustack/releases/tag/v2.2.2 (opens in a new tab)