# CVE-2026-102895: GPUStack Improper Authentication


- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 9 Nov 2026 (CISA KEV)
- **Fix available:** Yes
- **Published:** 4 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** GHSA-gj9m-f8ph-pmhr

## What is CVE-2026-102895?

CVE-2026-102895 is a critical vulnerability in gpustack, published on 4 Nov 2026. 

### Official description

GPUStack is an open-source GPU cluster manager for AI model serving and GPU instance provisioning. Prior to 2.2.0, get_current_user in gpustack/api/auth.py treated a loopback request source as the built-in administrator when force_auth_localhost was false, which was the default. A remote request could appear to originate from 127.0.0.1 because client_ip_getter accepted a same-host reverse proxy peer or a client-supplied X-GPUStack-Real-IP loopback value. The bypass allowed unauthenticated administrative access, including user and model changes, persistent administrator API-key creation, disclosure of worker and cloud-provider secrets, and code execution through POST /v2/inference-backends/from-yaml. Exploitation was observed in the wild against a 2.1.1 deployment. This issue is fixed in version 2.2.0.

Weakness: CWE-346 (Origin Validation Error), CWE-290 (Authentication Bypass by Spoofing), CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-102895?

1 open source package ship an affected version, including gpustack. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gpustack` | PyPI | All versions | 2.2.0 |

Products: Gpustack.

## How do I fix CVE-2026-102895?

Upgrade gpustack to 2.2.0 or later. US federal agencies must fix it by 12 Nov 2026.

## Is CVE-2026-102895 being exploited?

Yes. Attackers have exploited CVE-2026-102895 in the wild since at least 9 Nov 2026.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-102895 and fix it if it is affected.

What it is: CVE-2026-102895 is a critical vulnerability in gpustack, published on 4 Nov 2026. 
Exploitation: Yes. Attackers have exploited CVE-2026-102895 in the wild since at least 9 Nov 2026.

Affected packages and fixed versions:
- gpustack (PyPI): affected all versions; fixed in 2.2.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-102895/ (Markdown: https://insights.sbomify.com/CVE-2026-102895/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-102895
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-102895
- OSV: https://osv.dev/vulnerability/CVE-2026-102895

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-102895/
Summaries are generated and may contain mistakes; the official description above is the record.