Intel Hub

Threat intel

GPUStack auth bypass is exploited and listed in CISA KEV.

CVE-2026-102895 (CVSS 9.8) gives unauthenticated network attackers admin access to GPUStack servers before 2.2.0. CISA added it to KEV on November 9.

CISA added a GPUStack authentication bypass to its Known Exploited Vulnerabilities catalog on November 9, 2026. The flaw, tracked as CVE-2026-102895, lets an unauthenticated network attacker reach administrator functions on exposed GPUStack servers. GPUStack is an open-source manager for GPU clusters that serve AI models.


NVD scores the issue CVSS 3.1 9.8. It affects GPUStack versions before 2.2.0. Per the Cloud Security Alliance research note and other write-ups, the root cause is a default that treats requests arriving over loopback as admin. Behind a reverse proxy, that trust can be reached from the network. CISA's listing is titled "GPUStack Improper Authentication Vulnerability" and set a federal remediation due date of November 12.


Reporting on in-the-wild activity is thin. One report describes attacks against a server running version 2.1.1. Another says attackers used admin access to run reverse shells on AI servers. We could not confirm the actor or the scale of exploitation from the sources reviewed.


Why it matters. GPU inference hosts hold model weights, API keys and credentials for connected data stores, and they are often exposed to the internet in a hurry. Admin access on one of them can mean code execution, secret theft and a foothold in the training or data environment.


Mitigation. Upgrade to GPUStack 2.2.0 at minimum. Sources recommend 2.2.2, which also fixes a separate SAML bypass, CVE-2026-102894 (CVSS 9.1). Do not expose the management interface to the internet, and check what your reverse proxy forwards. Patching does not evict an attacker who is already in, so review admin account activity, API tokens, outbound connections and process launches on affected hosts for the period before the upgrade. Rotate any credentials stored on the server.

Sign-in required.

The full encrypted event log and the mitigation steps are available after sign-in.