GPUStack auth bypass CVE-2026-102895 exploited
CVE-2026-102895 is a trivial authentication-bypass vulnerability. GPUStack is also an attractive target. It is open-source software that manages clusters of GPUs, which are typically used to run AI wo
What Happened
SANS Internet Storm Center reported on Thursday, November 12th that it is observing active exploit attempts against an authentication bypass in GPUStack, tracked as CVE-2026-102895. The vulnerability is described as “trivial” to exploit, meaning it requires little skill or reconnaissance to abuse successfully. GPUStack is open-source software that manages clusters of GPUs, the hardware most commonly used to train and serve AI models.
The reporting does not attribute the activity to a specific actor. What matters is the timing: exploit attempts surfaced shortly after details became public, the pattern typical of automated scanning bots that sweep the internet for newly disclosed flaws.
Why It Matters
GPU clusters are high-value targets. They are expensive, often provisioned with cloud credentials and model weights attached, and frequently placed on networks with weaker perimeter controls than production application servers because they are treated as internal research infrastructure. An authentication bypass on the control plane of a GPU orchestrator hands an attacker the same access a legitimate administrator holds: the ability to schedule workloads, read environment variables, and reach every node the cluster manages.
This is not a data-confidentiality story in the abstract. Compromised GPU capacity can be repurposed for cryptomining or model theft, and stolen API keys tied to AI infrastructure can pivot into cloud accounts far beyond the original host.
Technical Details
The flaw is an authentication bypass, meaning a crafted request reaches protected API endpoints without valid credentials. SANS characterizes exploitation as trivial, which in practice means a single unauthenticated HTTP request, not a chained exploit. GPUStack exposes an API for cluster management, and that surface is what scanners are hitting.
Defenders should treat any GPUStack instance reachable from the internet as compromised until proven otherwise. Relevant indicators include unexpected workload submissions, new or modified user accounts in the GPUStack admin interface, and outbound connections from GPU nodes to unfamiliar destinations. Review authentication logs for successful API calls originating from addresses that never completed a login flow; those are the signature of a bypass rather than a credential attack.
Immediate Risk
Urgency is high for anyone running GPUStack with internet-exposed management interfaces. The barrier to entry is low, public reporting now exists, and scanning activity is confirmed. Organizations that deployed GPUStack internally should verify whether it is actually segmented from untrusted networks, since “internal” frequently means “reachable from the VPN or the corporate LAN.”
Patching to a fixed release is the primary mitigation. Where a fix is not yet applied, restrict the management API to known administrative source addresses and place it behind an authenticating reverse proxy. Yazoul maintains ongoing coverage of this exploitation activity in our GPUStack advisory.
Security Insight
The instructive comparison is Redis and, later, Ollama: both were convenience-first infrastructure tools that shipped with weak or absent authentication, both accumulated large internet-exposed footprints, and both became default targets for cryptominers within days of a bypass becoming public. GPUStack follows the same adoption curve, but the stakes are higher because the asset behind the door is not a cache but an AI compute cluster with cloud credentials attached.
The non-obvious takeaway is about inventory. Most organizations cannot answer how many GPUStack instances exist in their environment, let alone which are exposed. Attackers exploiting a trivial bypass do not need sophistication; they need one reachable host. Shadow AI infrastructure is now the softest part of many estates, and the control plane for it is where the next headline breach will come from.
Further Reading
Never miss a security update
Get real-time security alerts delivered to your preferred platform.
Related News
The ongoing campaign targeting ConnectWise ScreenConnect deployments involves the exploitation of a now-patched critical security flaw in the remote access software, and not a new vulnerability, it ha
The U.S. Cybersecurity and Infrastructure Security Agency (CISA) on Monday added four security flaws impacting GPUStack, SignalWire FreeSwitch, OpenBSD OpenSSH, and IBM Aspera Faspex to its Known Expl
The U.S. Cybersecurity and Infrastructure Security Agency (CISA) has added a high-severity vulnerability impacting SonicWall SonicOS to its Known Exploited Vulnerabilities (KEV) catalog, following rep