Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.8Exploited · CISA KEVamended

GPUStack: Authentication bypass via trusted loopback source (reverse-proxy TCP peer or X-GPUStack-Real-IP header) grants unauthenticated admin

CVE-2026-102895GHSA-gj9m-f8ph-pmhr

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (gpustack 2.2.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • PyPI gpustack

    Affected
    < 2.2.0
    Fixed in
    2.2.0

Sources

Severity and exploitation
Exploitation
Confirmed: listed in the CISA Known Exploited Vulnerabilities catalog.
CVSS
9.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
  • CVE-2026-102895: 0.56% estimated exploitation activity in the next 30 days; percentile 46.66 (FIRST EPSS, 2026-11-10). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Impact In GPUStack before v2.2.0, `get_current_user` (in `gpustack/api/auth.py`) promotes any request whose source is considered loopback to the built-in administrator account when `force_auth_localhost` is `False` (the default). The "source" is derived by `client_ip_getter`, which can be made to report `127.0.0.1` without any credentials in two ways: 1. Same-host reverse proxy (TCP peer). In the canonical self-hosted shape — GPUStack behind a same-host reverse proxy with `proxy_pass http://127.0.0.1: ` — every remote request arrives at GPUStack with TCP peer `127.0.0.1`, so the loopback auto-admin branch fires. No header or credential is required. Verified end-to-end against HEAD `6bee5883`. 2. `X-GPUStack-Real-IP` header. A forged `X-GPUStack-Real-IP: 127.0.0.1` header can cause the request source to be treated as loopback. Either path yields full, unauthenticated administrative access over the network: enumerate and modify users, models, workers, and configuration;…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from osv record GHSA-gj9m-f8ph-pmhr

  2. Revision 1 · created ·

    Published from ghsa record GHSA-gj9m-f8ph-pmhr

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-102895

Advisory: GPUStack: Authentication bypass via trusted loopback source (reverse-proxy TCP peer or X-GPUStack-Real-IP header) grants unauthenticated admin
IDs: CVE-2026-102895, GHSA-gj9m-f8ph-pmhr
Record: https://patchnext.com/advisories/cve-2026-102895 (revision 2, source checked 10 Nov 2026, 06:35 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.8)
Exploitation: confirmed: listed in the CISA Known Exploited Vulnerabilities catalog.
Vendor response: Vendor fix available; fixed versions by package: gpustack 2.2.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI gpustack: affected < 2.2.0; fixed in 2.2.0

## Suggested inspection (read-only)
- `python -m pip show gpustack`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on gpustack.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-gj9m-f8ph-pmhr (GitHub-reviewed advisory GHSA-gj9m-f8ph-pmhr lists affected ranges: PyPI gpustack >=0 <2.2.0)
- Verified: https://www.cisa.gov/known-exploited-vulnerabilities-catalog (CISA added CVE-2026-102895 to the Known Exploited Vulnerabilities catalog on 2026-11-09.)
- Verified: https://osv.dev/vulnerability/GHSA-gj9m-f8ph-pmhr (OSV record GHSA-gj9m-f8ph-pmhr lists affected ranges: PyPI gpustack >=0 <2.2.0 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…