Act nowVulnerabilities

GPUStack flaw lets anyone become admin and is already being exploited: CISA lists CVE-2026-102895. Upgrade to 2.2.0 or later

CVE-2026-102895 is a critical authentication bypass (CVSS 9.8) in GPUStack, an open source GPU cluster manager for serving AI models. Behind a reverse proxy on the same host, or with a forged header, a remote request is treated as the built-in admin. CISA added it to its exploited-vulnerabilities catalogue on 9 November. What is known and what to do.

Updated 11 Nov 2026: see what changed

How urgent

Act now

Who is affected

People who run GPUStack (the pip package gpustack) in a version below 2.2.0 and can be reached over a network, especially behind a reverse proxy on the same machine. The advisory says it was seen exploited against a 2.1.1 deployment. We did not read the release notes in full

What to do

Upgrade GPUStack to 2.2.0 or later (we suggest the latest 2.2.x, see below); until then set force_auth_localhost=true, strip the X-GPUStack-Real-IP header at your proxy and keep the API off untrusted networks; if it was exposed, rotate the cloud and worker secrets it held and look for custom backends you did not create

Published 11 Nov 2026 · Sources last checked 11 Nov 2026No. 77 / 87

Updates, follow-ups and corrections

  1. Update · 11 Nov 2026. First version of the story, based on the GitHub advisory for the flaw, the CVE record and CISA's catalogue of exploited flaws, read in a browser. We did not read the full v2.2.0 release notes, which do not mention the fix.

We keep the original text. When something changes, when we follow a story, or when we get something wrong, we add a dated note here instead of editing silently.

What happened

On 9 November 2026 CISA added CVE-2026-102895 to its catalogue of known exploited vulnerabilitiesVulnerability A weakness in software, a setting or a process that an attacker could use to get in or do harm. Tap again to open the glossary, under the name "GPUStack Improper Authentication Vulnerability". GPUStack is, per its README, an open source GPU cluster manager for AI model serving. The flaw is rated Critical, 9.8 out of 10. The GitHub advisory says it was observed exploited in the wild against a v2.1.1 deployment, where attackers created custom backends that ran reverse shells, and credits Javier Sixto for reporting the exploitation. CISA's catalogue lists a due date of 12 November for US federal agencies.

How it works, according to the advisory

GPUStack treated a request that appeared to come from the same machine (loopback) as the built-in administrator, unless the setting force_auth_localhost was turned on. It was off by default. A remote request could look local in two ways:

  • A reverse proxy on the same host. With a setting like proxy_pass http://127.0.0.1:<port>, every outside request reaches GPUStack from 127.0.0.1.
  • A forged header. An X-GPUStack-Real-IP: 127.0.0.1 header could make the request count as local.

The result is unauthenticated administrator access. The advisory lists changing users and models, creating long-lived admin API keys, disclosing worker and cloud-provider secretsSecret (API key, token, password) Any piece of text that proves to a service that you are allowed in, such as an API key, a database password or an access token. Tap again to open the glossary, and running code through an endpoint that accepts a backend definition.

How serious it is

Critical, and actively exploited, listed by CISA, with a fix available. That puts it at "act". If your GPUStack is on a network anyone can reach, assume it can be taken over.

What to do

  1. Upgrade GPUStack to 2.2.0 or later. The advisory lists versions below 2.2.0 as affected. Our advice: go to the latest 2.2.x, because a separate advisory (GHSA-3hch-x692-6qj3, CVE-2026-103002) covers a different authorization flaw fixed in 2.2.2. The two are different flaws.
  2. If you cannot upgrade yet, use the advisory's workarounds: set force_auth_localhost=true, make sure your proxy cannot make outside traffic look local and strip any client-supplied X-GPUStack-Real-IP header at the edge, and keep the API off untrusted networks (VPNVPN A private encrypted tunnel between your device and a network, so traffic does not travel in the open. Tap again to open the glossary or edge authentication).
  3. If it was reachable from the internet, assume it may have been used. Our advice, not from the advisory: look for custom backends you did not create, check for new admin API keys, and rotate the cloud-provider and worker secrets GPUStack held.
  4. Tell whoever runs your infrastructure that this flaw is already being used.

What we could not confirm

We read the GitHub advisory, the CVECVE A public ID number, like CVE-2026-12345, given to one specific security flaw so everyone can talk about the same bug. Tap again to open the glossary record and CISA's alert, and the v2.2.0 release page, which does not mention this fix in its notes. The advisory does not say whether the default of the setting changed in 2.2.0, nor in words whether the forged-header route works without any proxy. The release page shows a date of 18 June without a year, while the advisory is dated 31 July 2026 and the CVE record 4 November, so we cannot tell exactly when the fix shipped. Nobody has said who is behind the attacks or how many installations were hit. We have not tested it ourselves.

Watch the short video

The video loads from YouTube (privacy-enhanced mode) only when you press play.

Comments

No account needed. Add a nickname if you like, or leave it empty to comment anonymously. Comments are reviewed before they appear. Links are not allowed.

    We store your comment, your nickname and a scrambled form of your connection that we use only to limit spam. We do not store your IP address or set cookies. Cloudflare Turnstile checks that you are not a bot.

    Sources and verification

    We use primary sources first and say when we rely on a news report. Dates are the day we last checked each source.

    Spotted a mistake? Email [email protected] and we will correct it and note the change.

    Get the free runbooks

    One-page security checklists for founders who build with AI. You get a confirmation email first, then the runbooks.

    Send me the runbooks