Quick answers
- Is CVE-2026-102894 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-102894 being exploited in the wild.
- How severe is CVE-2026-102894?
- Critical severity, with a CVSS score of 9.1, published 4 November 2026.
- Which products and versions are affected?
- gpustack (PyPI) >= 0.7.1, < 2.2.2, ECOSYSTEM:introduced=0.7.1,fixed=2.2.2; GPUStack 0.7.1 to 2.2.1.
- Is there a fix for CVE-2026-102894?
- Yes. gpustack (PyPI): upgrade to 2.2.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-102894 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-102894?
- Check whether you run gpustack (PyPI) or GPUStack at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- gpustack (PyPI): upgrade to 2.2.2 or later
pip install "gpustack>=2.2.2"
Technical details
The /auth/saml/callback endpoint parsed SAML XML responses and extracted NameID and attributes without calling OneLogin_Saml2_Auth.process_response(), skipping verification of the signature, issuer, audience, destination, and time conditions. An unauthenticated attacker could submit a hand-crafted SAML response to impersonate existing users or provision new accounts, even when SAML was not configured. Signed responses could be replayed since assertion identifiers were not consumed.
Affected products
- GPUStack 0.7.1 to 2.2.1
Identifiers
- CVE-2026-102894
- GHSA-62m9-f875-rqw6
Timeline
- 2026-11-04: disclosed