Security Digest · Vulnerability record
CVE-2026-102894: GPUStack: SAML callback trusts an unverified SAMLResponse, allowing authentication bypass and account takeover
GPUStack is an open-source GPU cluster manager for AI model serving and GPU instance provisioning.
CVSS 9.1 Critical EPSS 0.3% · p25
Should you act?
Critical and remotely reachable
No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.
- No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
- EPSS 0.3%, percentile 25: FIRST’s model estimates a 0.3% chance of exploitation activity in the next 30 days, higher than 25% of all scored CVEs (low). EPSS is a probability, not a verdict.
- Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
- Only applies if your dependency tree includes
gpustack(PyPI) >= 0.7.1, < 2.2.2, fixed in 2.2.2. Check your lockfile, including transitive dependencies.
What it is
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 gpustacksession JWT without calling OneLoginSaml2Auth.processresponse 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.
From the GitHub advisory
Impact
The callback Base64-decodes the posted XML, reads NameID and attributes, resolves or provisions the user, and mints a gpustacksession JWT — but never calls OneLoginSaml2Auth.processresponse(), 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:
- If the name matches an existing user (e.g. an administrator), the attacker receives that user's session — full account takeover, including administrator access. - Otherwise, a new non-admin user is provisioned.
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.
Weakness type: CWE-294, CWE-347.
Product: gpustack (PyPI) · Assigned by: GitHub_M · Published: 2026-11-04
Affected and fixed versions
| Ecosystem | Package | Vulnerable | First fixed |
|---|---|---|---|
| PyPI | gpustack | >= 0.7.1, < 2.2.2 | 2.2.2 |
| Vendor | Product | Affected versions (per CVE record) |
|---|---|---|
| gpustack | gpustack | >= 0.7.1, < 2.2.2 |
Severity scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| GitHub_M | 3.1 | 9.1 Critical | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
| GitHub | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
- Attack vector: network (remotely reachable)
- Attack complexity: low
- Privileges required: none (no login)
- User interaction: none
- Scope: unchanged
CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.
Exploitation and urgency
- CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
- CISA SSVC assessment: exploitation none, automatable yes, technical impact total.
- FIRST EPSS (model of 2026-11-21): 0.32% probability of exploitation activity in the next 30 days; percentile 25.
Timeline
- — CVE record published by GitHub_M
- — CVE record last updated
- — GitHub-reviewed advisory GHSA-62m9-f875-rqw6 published (critical)
Sources and references
Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.
Vulnerability records
- GitHub Advisory GHSA-62m9-f875-rqw6 github.com
- CVE.org record CVE-2026-102894 cve.org
- NVD entry CVE-2026-102894 nvd.nist.gov
Other references from the CVE record and advisory
- github.com github.com
- github.com github.com
- github.com github.com
- github.com github.com
- github.com github.com
- github.com github.com