Skip to content
securitytabs

LiveUpdated

GPUStack authentication bypass added to CISA exploited list as scans continue

A flaw in GPUStack, open-source software that manages computers used for AI workloads, lets an attacker skip the login on exposed systems, and attackers are using it. Organizations running GPUStack should update now.

GPUStack login bypass exploited in attacks
GPUStack login bypass exploited in attacks

What's new

Newest coverage

TimelineWhat should my organization do?

Vulnerabilities

What happened

CISA added CVE-2026-102895, an improper authentication flaw in GPUStack, to its Known Exploited Vulnerabilities (KEV) catalogue, its list of flaws attackers are using, on 9 November 2026, citing evidence of active exploitation. NVD rates the flaw 9.8 on the CVSS scale. CISA's federal due date was 12 November. [1]

GPUStack is open-source software that manages clusters of GPUs, which are typically used to run AI workloads. The SANS Internet Storm Center describes the bug as a trivial authentication bypass. [2]

How the flaw works

SANS says an attacker can bypass authentication by spoofing the X-GPUStack-Real-IP header with the loopback address, so the request appears to come from the machine itself. Exploitation is trivial on an exposed system, it says. [3]

Exploitation and fixes

The SANS Internet Storm Center reports exploit attempts and scans against GPUStack. All versions before 2.2.0 are affected. SANS says the flaw was not made public until the end of July and the CVE identifier was assigned on 4 November. [2][3]

CISA's KEV listing records the ransomware use of this flaw as unknown. [1]

Timeline

  1. SANS described scans for the GPUStack authentication bypass. [3]

  2. The SANS Internet Storm Center reported exploit attempts against GPUStack. [2]

  3. CISA added the GPUStack flaw to its Known Exploited Vulnerabilities catalogue. [1]

Explained

The technology and terms in this story. Learn more

Why it was possible

The weaknesses behind this story's CVEs, from each CVE Record.

Business ActionWhat this means inside your organization, and what to do about it, by company size.

Small business

No dedicated security staff; relies on providers

What to know

Most small businesses will not run GPUStack directly, but a provider hosting AI workloads might. Versions before 2.2.0 are affected. [2]

What to do

  1. Ask your IT or hosting provider whether GPUStack is in use and whether it is on version 2.2.0 or later. [2]
  2. If you run GPUStack yourself, update it to version 2.2.0 or later. [2]

Mid-size company

A small IT or security team

What to know

CISA lists the flaw as exploited, and SANS says exploitation of an exposed system is trivial. [1][3]

What to do

  1. Find GPUStack installs and update any version before 2.2.0. [2]
  2. Check whether GPUStack is reachable from the internet and review its access logs for requests carrying the X-GPUStack-Real-IP header. [3]

Large enterprise

A security operations team

What to know

GPU clusters for AI are an attractive target, according to SANS, and exploit attempts are being observed. [2]

What to do

  1. Inventory GPUStack deployments, including in research and development teams, and move them to version 2.2.0 or later. [2]
  2. Hunt for requests with a spoofed X-GPUStack-Real-IP header in reverse-proxy logs. [3]

Sources

  1. [1]CISA Advisories · Nov 9, 12:00 UTC
    CISA Adds Four Known Exploited Vulnerabilities to Catalogcontext
  2. [2]US-CERT / SANS Internet Storm Center · Nov 12, 11:50 UTC
    Exploit Attempts for GPUStack Authentication Bypass (CVE-2026-102895), (Thu, Nov 12th)context
  3. [3]SANS Internet Storm Center StormCast · Nov 13, 02:00 UTC
    SANS Stormcast Friday, November 13th, 2026: GPUStack Auth Bypass Scans (CVE-2026-102895); ConnectWise ScreenConnect Advisory; N-able N-central Exploits; Microsoft 365 Outagecontext