# CVE-2026-102894: GPUStack: SAML callback trusts an unverified SAMLResponse, allowing authentication bypass and account takeover


- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 4 Nov 2026
- **Updated:** 6 Nov 2026
- **Also known as:** GHSA-62m9-f875-rqw6

## What is CVE-2026-102894?

CVE-2026-102894 is a critical vulnerability in gpustack, published on 4 Nov 2026. 

### Official description

GPUStack is an open-source GPU cluster manager for AI model serving and GPU instance provisioning. From 0.7.1 until 2.2.2, the /auth/saml/callback endpoint decoded SAML XML, used its NameID and attributes to resolve or provision a user, and minted a gpustack_session JWT without calling OneLogin_Saml2_Auth.process_response to verify the signature, issuer, audience, destination, or time conditions. Any network client could submit an identity for an existing user, including an administrator, or provision a new non-administrator account, even when SAML was not configured. Response and Assertion identifiers were not consumed, so captured signed responses could also be replayed. This issue is fixed in version 2.2.2.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature), CWE-294 (Authentication Bypass by Capture-replay)

## Which versions are affected by CVE-2026-102894?

1 open source package ship an affected version, including gpustack.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gpustack` | PyPI | From 0.7.1 | 2.2.2 |

## How do I fix CVE-2026-102894?

Upgrade gpustack to 2.2.2 or later.

## Is CVE-2026-102894 being exploited?

There is no known exploitation of CVE-2026-102894 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-102894 and fix it if it is affected.

What it is: CVE-2026-102894 is a critical vulnerability in gpustack, published on 4 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-102894 in the wild and no public exploit code.

Affected packages and fixed versions:
- gpustack (PyPI): affected from 0.7.1; fixed in 2.2.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-102894/ (Markdown: https://insights.sbomify.com/CVE-2026-102894/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-102894
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-102894
- OSV: https://osv.dev/vulnerability/CVE-2026-102894

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-102894/
Summaries are generated and may contain mistakes; the official description above is the record.