CVSS 3.1
9.8 criticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HCVE-2026-102895
Critical (9.8).
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.
Severity
- CWEs
- CWE-287 Improper Authentication
CWE-290 Authentication Bypass by Spoofing
CWE-346 Origin Validation Error - OWASP Top 10
- A07:2025 Authentication Failures
- Published
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-102895 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-102895?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-102895?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-102895 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| gpustack | < 2.2.0 |
Attack patterns (CAPEC)
- CAPEC-22 Exploiting Trust in Client Likelihood: High · Severity: High
- CAPEC-57 Utilizing REST's Trust in the System Resource to Obtain Sensitive Data Likelihood: Medium · Severity: Very High
- CAPEC-94 Adversary in the Middle (AiTM) Likelihood: High · Severity: Very High
- CAPEC-114 Authentication Abuse Severity: Medium
- CAPEC-115 Authentication Bypass Severity: Medium
- CAPEC-151 Identity Spoofing Likelihood: Medium · Severity: Medium
- CAPEC-194 Fake the Source of Data Severity: Medium
- CAPEC-593 Session Hijacking Likelihood: High · Severity: Very High
- CAPEC-633 Token Impersonation Severity: Medium
- CAPEC-650 Upload a Web Shell to a Web Server Severity: High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-290, CWE-346 (16).