Skip to content
NewCybercrime Report 2026 · Eight Chapters · A Post Is Not An Incident → Explore The ChaptersCybercrime Report 2026 → Explore

GPUStack Loopback Authentication Bypass (CVE-2026-102895)

CVE-2026-102895 is an authentication bypass in GPUStack, an open-source GPU cluster manager for AI model serving.

Published
Reading Time
3 min read
Dark glass server rack with one cabinet door open, a single cold blue indicator light beside its lock, red neon lines, cover art for: GPUStack Loopback Authentication Bypass (CVE-2026-102895)

GitHub, the CNA, scores it CVSS 3.1 9.8 Critical. CISA added it to the Known Exploited Vulnerabilities catalog on 9 November 2026, and the fix shipped in GPUStack 2.2.0.

What it allows

CVE-2026-102895 is an authentication gap in GPUStack, an open-source GPU cluster manager for AI model serving and GPU provisioning. The advisory says the function that identifies a caller, get_current_user, treats a request as the built-in administrator whenever the request appears to come from the loopback (localhost) address.
GPUStack does not ask that caller for a password in that case, under a setting named force_auth_localhost that defaults to false. The advisory names two ways a remote caller can make a request look like it came from loopback.
One is a same-host reverse proxy in front of GPUStack, where every proxied connection already looks like it originates from loopback. The advisory separately says GPUStack also trusted a caller-supplied signal that claimed the same origin. We leave out the exact mechanics on purpose.
What CVE-2026-102895 Allows an Attacker to Do
The advisory says either path grants full unauthenticated administrative access over the network. It lists the ability to enumerate and change users, models and workers, to create administrator API keys that stay valid afterward, and to read worker credentials and cloud-provider secrets.
The advisory adds that this access reaches an admin-only function that builds a new inference backend from a supplied configuration, and that the path can run code on worker machines. Our least privilege entry explains the control this flaw removes. GitHub's advisory states that exploitation was observed in the wild against a GPUStack 2.1.1 deployment, where an attacker created custom backends that ran reverse shells.
How the Score Reads
GitHub, the CNA, scores it CVSS 3.1 9.8 Critical, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. There is no CVSS 4.0 score in the record or NVD. NVD lists the entry as Analyzed, first published 4 November 2026.
The weaknesses the advisory gives are CWE-287 (improper authentication), CWE-290 (authentication bypass by spoofing) and CWE-346 (origin validation error). See our CVSS entry for how to read the vector.
What the Maintainers and CISA KEV Say
The advisory names 2.2.0 as the first fixed release and says it removes the loopback administrator path. CISA added CVE-2026-102895 to the Known Exploited Vulnerabilities catalog on 9 November 2026, with a remediation due date of 12 November 2026. Our KEV glossary entry explains the catalog.

Who is affected

The advisory lists the gpustack Python package before 2.2.0 as affected and names 2.2.0 as the fixed release. GitHub's release page dates 2.2.0 to 18 June 2026, well before the advisory and the CISA KEV listing.

GitHub's pull request record shows the fix itself. The maintainers titled it removing the loopback auto-admin path, and merged it on 19 May 2026, a month before the 2.2.0 release that shipped it.
The advisory credits Nikko Enggaliano, Wei Yunzhou, and Rui Yang and Haoyu Wang of Johns Hopkins University as independent finders of the authentication gap. It credits a separate researcher, Javier Sixto, for reporting the in-the-wild exploitation. Our Kubeflow Pipelines authorization bypass entry covers a similar access-control gap in another self-hosted AI platform.

Timeline

  1. 19 May 2026

    GitHub records the merge of the pull request that removes the loopback auto-admin path, per the pull request's own history.

  2. 18 Jun 2026

    GPUStack 2.2.0, which ships that fix, is released, per the GitHub release page.

  3. 4 Nov 2026

    NVD publishes the CVE record for CVE-2026-102895.

  4. 9 Nov 2026

    GitHub publishes advisory GHSA-gj9m-f8ph-pmhr, and CISA adds the CVE to the Known Exploited Vulnerabilities catalog with a 12 November 2026 remediation due date.

What to do

  1. Upgrade to GPUStack 2.2.0 or Later

    Move every GPUStack deployment to 2.2.0 or later, as the advisory directs. That release removes the loopback administrator path the advisory describes.

  2. Set force_auth_localhost to True if You Cannot Upgrade Yet

    The advisory lists this setting as a workaround, so GPUStack asks for credentials even on a request that looks like it comes from the loopback address.

  3. Review the Reverse Proxy in Front of GPUStack

    The advisory says a same-host reverse proxy can itself make an external request look like it came from loopback. Check the proxy configuration before trusting any address-based signal from the public side.

  4. Rotate Admin API Keys and Worker Secrets

    The advisory says the bypass let an attacker create administrator API keys and read worker and cloud-provider secrets. We recommend rotating every administrator key and worker credential issued before the upgrade.

  5. Prioritize Any 2.1.1 Deployment

    GitHub's advisory states that exploitation was observed in the wild against a GPUStack 2.1.1 deployment. CISA's Known Exploited Vulnerabilities catalog sets a remediation due date of 12 November 2026 for this CVE.

Frequently Asked Questions

Which GPUStack versions does CVE-2026-102895 affect?

The advisory lists every version before 2.2.0 as affected. GPUStack 2.2.0, released 18 June 2026, fixes it.

Does an attacker need a password or an account?

No. The advisory describes an unauthenticated bypass that makes a remote request look like it comes from the loopback address.

Has CVE-2026-102895 been exploited?

GitHub's advisory states that exploitation was observed in the wild against a GPUStack 2.1.1 deployment, and CISA added the CVE to its Known Exploited Vulnerabilities catalog on 9 November 2026.

What if I cannot upgrade to 2.2.0 right away?

The advisory lists setting force_auth_localhost to true as a workaround, plus checking that no reverse proxy or edge signal lets an external caller look like loopback.

Is CVE-2026-102895 in the CISA KEV catalog?

Yes. CISA added it on 9 November 2026, catalog version 2026.11.09, with a remediation due date of 12 November 2026.

Sources

  1. CVE-2026-102895NVD
  2. GHSA-gj9m-f8ph-pmhr, Authentication bypass via trusted loopback source grants unauthenticated adminGPUStack on GitHub
  3. Known Exploited Vulnerabilities CatalogCISA
  4. GPUStack 2.2.0 release notesGPUStack on GitHub
  5. Pull request 5346, remove the localhost auto-admin bypass GPUStack on GitHub
ShareLinkedInX
Brandefense logo

Stay Ahead of Digital Threats.

Take control of your digital security with an exclusive demo of our AI-driven threat intelligence platform.

Open The Full Demo Form →