Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.1amended

GPUStack: SAML callback trusts an unverified SAMLResponse, allowing authentication bypass and account takeover

CVE-2026-102894GHSA-62m9-f875-rqw6

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (gpustack 2.2.2), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • PyPI gpustack

    Affected
    >= 0.7.1, < 2.2.2
    Fixed in
    2.2.2

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
9.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS
  • CVE-2026-102894: 0.26% estimated exploitation activity in the next 30 days; percentile 17.65 (FIRST EPSS, 2026-11-10). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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: - 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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from osv record GHSA-62m9-f875-rqw6

  2. Revision 1 · created ·

    Published from ghsa record GHSA-62m9-f875-rqw6

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-102894

Advisory: GPUStack: SAML callback trusts an unverified SAMLResponse, allowing authentication bypass and account takeover
IDs: CVE-2026-102894, GHSA-62m9-f875-rqw6
Record: https://patchnext.com/advisories/cve-2026-102894 (revision 2, source checked 11 Nov 2026, 07:05 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: gpustack 2.2.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI gpustack: affected >= 0.7.1, < 2.2.2; fixed in 2.2.2

## Suggested inspection (read-only)
- `python -m pip show gpustack`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on gpustack.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-62m9-f875-rqw6 (GitHub-reviewed advisory GHSA-62m9-f875-rqw6 lists affected ranges: PyPI gpustack >=0.7.1 <2.2.2)
- Verified: https://osv.dev/vulnerability/GHSA-62m9-f875-rqw6 (OSV record GHSA-62m9-f875-rqw6 lists affected ranges: PyPI gpustack >=0.7.1 <2.2.2 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…