CVE-2026-102895

CVE Enrichment

CVSS: 9.8 CRITICAL
EPSS: 0.33%
EPSS Percentile: 26.46%
CISA KEV: YES — Known Exploited Vulnerability

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.

Technical Details

CVSS Version: 3.1
CNA / NVD Source: [email protected]
Published: 05-Nov-2026 05:17
Last Modified: 10-Nov-2026 12:17
EPSS Date: 2026-11-09
CWE: CWE-287, CWE-290, CWE-346

CVSS Vector


            CVSS:3.1                            AV:N /
                            AC:L /
                            PR:N /
                            UI:N /
                            S:U /
                            C:H /
                            I:H /
                            A:H

CISA KEV Details

Date Added: 2026-11-09
Remediation Due: 2026-11-12
Known Ransomware Campaign Use: Unknown
Required Action: 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.
Notes: This vulnerability affects an open-source component, third-party library, protocol, or proprietary implementation that could be used by different products. For more information, please see: ; https://github.com/gpustack/gpustack/security/advisories/GHSA-gj9m-f8ph-pmhr ; BOD 26-04: https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk ; Forensics Triage Requirements: 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

CNA Products / Version Status

gpustack · gpustack Source: CNA · [email protected]
Default status: unknown

< 2.2.0 — affected

Affected Products / Versions

gpustack / gpustack Source: NVD CPE · affected
Version / affected range: * · before (exclusive) 2.2.0
cpe:2.3:a:gpustack:gpustack:*:*:*:*:*:*:*:*

References

Last enrichment sync: 10-Nov-2026 14:01
Sources: NVD · FIRST EPSS · CISA KEV
Latest successful provider update; providers refresh independently.

Reported Context (3)

Tracked as CVE-2026-102895 (CVSS score of 9.8), the GPUStack bug could allow remote, unauthenticated attackers to gain full administrative access to vulnerable servers. CISA Warns of Exploitation of IBM Aspera Faspex and FreeSWITCH Flaws
In an advisory for CVE-2026-102895 published on July 31, 2026, the maintainers of the GPUStack Python package credited Nikko Enggaliano, Wei Yunzhou, Rui Yang, and Haoyu Wang for independently reporting the flaw, adding CISA Adds Four Product Flaws to KEV Catalog, Citing Active Exploitation
CVE-2026-102895 GPUStack Improper Authentication Vulnerability CISA Adds Four Actively Exploited Vulnerabilities to KEV Catalog

CVE (3)

Malware (1)

People (5)

Threat Actors (1)

MITRE ATT&CK (6)

Vendors (4)

Products (4)

Note: Related entities, including threat actors, malware, CVEs, MITRE ATT&CK techniques, vendors, products, tools, countries, and industries, are shown when they appear in the same reporting. Their presence does not necessarily mean they were targeted, compromised, vulnerable, responsible for the activity, or directly involved in the incident.