Exploited in the wild

CVE-2026-102895: GPUStack Authentication Bypass Exploited

Inttelio Threat Feeds ·

GPUStack versions prior to 2.2.0 treat requests that appear to come from 127.0.0.1 as the built-in administrator by default, and attackers can fake that loopback origin remotely. This gives unauthenticated administrative access, including secret disclosure and code execution. CISA added the flaw to its Known Exploited Vulnerabilities catalog on 2026-11-09, and the fix is GPUStack 2.2.0.

CVECVE-2026-102895
Vendor / productGPUStack GPUStack
CVSS v3.19.8 CRITICAL
WeaknessCWE-287, CWE-290, CWE-346
Exploited in the wildYes - added to CISA KEV November 9, 2026
CISA due date (federal agencies)November 12, 2026
PublishedNovember 4, 2026

Who is affected

Organizations running GPUStack, the open-source GPU cluster manager for AI model serving and GPU instance provisioning, on any version prior to 2.2.0. Deployments where force_auth_localhost is false, which is the default, are affected. The risk is highest where GPUStack sits behind a reverse proxy on the same host, or where clients can send an X-GPUStack-Real-IP header that reaches the server. Exploitation was observed against a 2.1.1 deployment. CISA notes the flaw affects an open-source component that other products could use, so check whether any software you run bundles GPUStack.

What attackers can do

An unauthenticated remote attacker can make a request look like it came from 127.0.0.1. They can do this through a same-host reverse proxy, or by supplying a loopback value in the X-GPUStack-Real-IP header. GPUStack then treats the request as the built-in administrator. With that access the attacker can change users and models, create persistent administrator API keys, and read worker and cloud-provider secrets. They can also execute code through POST /v2/inference-backends/from-yaml. The CVSS 3.1 base score is 9.8 (Critical): network attack, low complexity, no privileges or user interaction required.

Exploitation status

Exploited in the wild. The NVD description states exploitation was observed against a GPUStack 2.1.1 deployment. CISA added CVE-2026-102895 to the KEV catalog on 2026-11-09 with a due date of 2026-11-12 and flagged it for forensic triage. That deadline binds U.S. federal civilian agencies under BOD 26-04. Other organizations should treat it as a strong signal of urgency. Known ransomware campaign use is listed as Unknown. The source data includes no threat actor attribution or indicators of compromise.

What to do now

  1. Upgrade every GPUStack instance to version 2.2.0 or later. Review the vendor advisory GHSA-gj9m-f8ph-pmhr and the v2.2.0 release notes on GitHub for any further vendor instructions.
  2. If you cannot upgrade immediately, remove GPUStack from internet exposure or restrict access to trusted networks. The source data does not list an official workaround, so check the vendor advisory before relying on configuration changes such as setting force_auth_localhost to true.
  3. Strip or block any client-supplied X-GPUStack-Real-IP header at your reverse proxy or edge, and review how a same-host proxy forwards client addresses.
  4. Assume compromise on any pre-2.2.0 instance that was reachable from untrusted networks, because CISA has flagged this vulnerability for forensic triage. Review all administrator API keys and user accounts, and revoke any you did not create.
  5. Check for unexpected model or user changes, and look for requests to POST /v2/inference-backends/from-yaml and other administrative endpoints in proxy and application logs.
  6. Rotate all worker credentials and cloud-provider secrets stored in or reachable by GPUStack, since these may have been disclosed.
  7. If you find signs of compromise, investigate the GPUStack host and connected GPU workers for code execution. Follow CISA's Forensics Triage Requirements guidance where applicable.
  8. Inventory all GPUStack deployments, including copies bundled in other products or set up by data science teams outside normal IT processes. Confirm each one is on 2.2.0 or later.

Frequently asked questions

Which GPUStack versions are vulnerable to CVE-2026-102895?

All versions prior to 2.2.0 are affected when force_auth_localhost is false, which is the default setting. Exploitation was observed against version 2.1.1. The issue is fixed in GPUStack 2.2.0.

Is CVE-2026-102895 being exploited?

Yes. The NVD description reports exploitation in the wild against a 2.1.1 deployment, and CISA added the flaw to its Known Exploited Vulnerabilities catalog on 2026-11-09 with a due date of 2026-11-12. Whether it has been used in ransomware campaigns is listed as unknown.

How does the GPUStack localhost authentication bypass work?

GPUStack's get_current_user function treated requests from a loopback address as the built-in administrator. The client IP logic accepted a same-host reverse proxy as the source, or trusted a client-supplied X-GPUStack-Real-IP header set to a loopback value. Either way, a remote attacker could appear to be 127.0.0.1 and gain full admin access without logging in.

Sources

This briefing was drafted with AI from the official NVD and CISA records. Always confirm affected versions and fixes in the vendor advisory.

Not sure if you are exposed?

Our penetration testers find exploitable flaws before attackers do, and a vCISO can run your vulnerability program.

Talk to Inttelio