CVE-2026-102895: GPUStack Improper Authentication Vulnerability
- Is it exploited?
Yes. CISA added it to the Known Exploited Vulnerabilities catalog on , 5 days after the CVE record was published.
VulnCheck KEV lists it since , 101 days before CISA. It cites 3 public reports, the first from .
- How likely is exploitation in the next 30 days?
- 0.5%
EPSS score, percentile 44.5 of all scored records
- How severe?
- 9.8 Critical
CVSS v3.1 base score, given by the CNA
- What should I do?
No patch or vendor advisory is listed in the CVE record. Check GPUStack's advisories.
CISA (deadline ): Apply mitigations in accordance with vendor instructions … Full text
- Which versions are affected?
Affected
- < 2.2.0
Source: CISA KEV 2026.11.10, as of ; VulnCheck KEV, as of ; FIRST EPSS, as of ; CVE List, as of . About the data.
Description
GPUStack: Authentication bypass via trusted loopback source (reverse-proxy TCP peer or X-GPUStack-Real-IP header) grants unauthenticated admin
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.
Source: CVE List, as of . About the data.
What to do
Advisories and patches
No patch, vendor advisory or mitigation is listed in the CVE record. Check GPUStack's own security advisories for a fix, and compare your version with the affected versions below.
Required action, set by CISA
Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
CISA due date for this action: .
Linked from CISA's catalog entry
- https://github.com/gpustack/gpustack/security/advisories/GHSA-gj9m-f8ph-pmhr
- https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk
- https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk
- https://nvd.nist.gov/vuln/detail/CVE-2026-102895
This summary is based on the CVE record and CISA's catalog entry as of . Check the vendor's advisory before you act: affected versions and fixes can change.
Affected products and versions
Versions by product, as listed in the CVE record (1 product)
| Status | Versions |
|---|---|
| Affected | < 2.2.0 |
Source: CVE List, as of . About the data.
Weakness
CWE-287, CWE-290, CWE-346
- CWE-287: Improper Authentication
- CWE-290: Authentication Bypass by Spoofing
- CWE-346: Origin Validation Error
CWE and CAPEC are maintained by MITRE; the entries are those named in the CVE record and the KEV entry.
Timeline
| Date | Event |
|---|---|
| CVE record published | |
| Added to CISA KEV | |
| CVE record last updated | |
| CISA due date for the required action |