GPUStack is an open source GPU cluster manager for model serving 1. Before 2.2.0, its API carried a shortcut for the person sitting at the console. get_current_user in gpustack/api/auth.py promoted any request whose source it read as loopback to the built-in administrator, as long as force_auth_localhost was false, which it was by default 2.

The source came from client_ip_getter, and the advisory names two ways to make that function answer 127.0.0.1 without a credential 2. The first is the shape the advisory calls canonical, with GPUStack behind a reverse proxy on the same host and proxy_pass http://127.0.0.1:<port>. Every remote request then arrives with a loopback TCP peer, so the administrator branch fires for each of them. The second is a forged X-GPUStack-Real-IP: 127.0.0.1.

What the administrator seat reaches

An unauthenticated caller who lands in that seat can list and change users, models, workers, and configuration. Two of the consequences in the advisory matter more to me than the account editing. The caller can mint persistent administrator API keys with scope ["*"] that keep working from any source address afterwards, and can read worker credentials and cloud provider secrets 2. With an administrator session, POST /v2/inference-backends/from-yaml deploys a custom backend to worker hosts, which is code execution there 2.

The advisory records exploitation against a 2.1.1 deployment, with attacker-created custom backends running reverse shells 2. CISA added the CVE to the KEV catalog on 9 November with a due date of 12 November 3. NVD published its record on 4 November from the GitHub CNA, which rates it 9.8 with no privileges and no user interaction 1.

The fix is older than the deadline

Version 2.2.0 shipped on 18 June 4. The advisory went public on 31 July 2, NVD’s record followed on 4 November 1, and the KEV entry arrived on 9 November 3. A three day window on a fix that shipped in June points at a host nobody upgraded after June.

That changes what goes in my note to the teams. The question worth answering is which hosts run GPUStack at all, and who can name the version without opening a shell on the box. A server still below 2.2.0 has been reachable through a published administrative bypass since the end of July.

Why loopback stopped meaning the operator

The person who wrote that branch was reasoning about a socket. A request from 127.0.0.1 came from the machine itself, and on a single host install that meant an operator who already had shell access. The reasoning holds until a reverse proxy enters the picture, because a proxy on the same host connects to the upstream over loopback for every request it forwards, including the requests it received from the internet. The address stays the same while the meaning changes underneath it.

The header path catches me out more. X-GPUStack-Real-IP is the application’s own header, not one of the standard forwarding headers, and the rules I write at an edge list the standard ones. My configs overwrite X-Forwarded-For, X-Real-IP, and Forwarded for the services they front. None of those rules anticipated a name the application invented for itself, so the forged header reaches the API unless somebody writes a rule for it.

What the upgrade does to the emergency step

The obvious mitigation is to set force_auth_localhost=true and keep working, and the advisory lists it along with stripping the header at the edge and keeping the API off untrusted networks 2. On 2.2.0 that setting no longer exists. The pull request that closed the flaw removed the force-auth-localhost option outright and moved the password reset CLI onto a short lived JWT minted from the local server’s secret 5.

My upgrade note carries two lines that will read as contradictions to whoever works the ticket. The mitigation they apply today is gone tomorrow, and the local recovery path they memorized has changed. The automated review on that pull request flagged the risk in the other direction, noting that removing the local request check left the configuration update endpoint with no authorization gate and asking for an administrator dependency on the function 5. Removing the shortcut left the endpoint exposed somewhere else, and the reviewer caught it before the merge.

What I check on a service behind a proxy

I read the version the running server reports, on the server, rather than the tag in a deployment file. A pinned tag records what someone intended to run.

I trace how the app decides the client address. If the answer is a header, I find out who strips it, and I check whether that party sits in front of every path to the app, including the management port.

I search the edge configuration for the application’s own header names. A name I have never seen does not appear in a rule set I wrote before it existed.

I map where the authenticated paths are reachable from. A login form published to the internet and an admin API published to the internet share an exposure when the authentication branch can be skipped, and the bypass never touches the login form.

What the patch does not remove

The upgrade closes the branch. It does not revoke the keys the branch could have minted, and it does not remove a custom inference backend that somebody else added. Both survive a version bump, so the same ticket needs a second half. List the administrator API keys and match them to owners, list the inference backends and match them to whoever asked for them, and treat the credentials and cloud provider secrets the server held as exposed if the host was reachable from an untrusted network.

The KEV due date gives me a deadline for the upgrade. The audit of what the bypass could have left behind is the part I would start today, because a host that gets patched on 12 November still carries whatever was minted during the months it was not.


  1. National Vulnerability Database. (2026, November 4). CVE-2026-102895 detail. National Institute of Standards and Technology. https://nvd.nist.gov/vuln/detail/CVE-2026-102895 ↩︎ ↩︎ ↩︎

  2. GitHub. (2026, July 31). Authentication bypass via trusted loopback source (reverse-proxy TCP peer or X-GPUStack-Real-IP header) grants unauthenticated admin (GHSA-gj9m-f8ph-pmhr). GitHub Security Advisories. https://github.com/gpustack/gpustack/security/advisories/GHSA-gj9m-f8ph-pmhr ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎

  3. Cybersecurity and Infrastructure Security Agency. (2026, November 9). Known exploited vulnerabilities catalog (CVE-2026-102895). https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-102895 ↩︎ ↩︎

  4. GitHub. (2026, June 18). Release v2.2.0. https://github.com/gpustack/gpustack/releases/tag/v2.2.0 ↩︎

  5. GitHub. (2026, May 19). refactor: remove localhost auto-admin bypass (Pull request #5346). https://github.com/gpustack/gpustack/pull/5346 ↩︎ ↩︎