Skip to content
Vulnerabilities

CVE-2026-102895

Confirmed exploited in the wild Exploited

GPUStack GPUStack — GPUStack Improper Authentication Vulnerability

Why it matters

Exploited in the wild · public exploit available · patch/mitigation per vendor

What to do

Apply the vendor's fix or mitigation now, starting with internet-facing systems, and check logs for signs of exploitation.

9.8
Severity · CVSS 3.1 critical
0.5%
Chance of exploitation in 30 days (EPSS) · top 55.5%
active
Exploitation status · automatable: yes
1
Public PoC repositories

Description

Published 2026-11-04

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.

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

Exploit & advisory signals

Critical CVSS 9.8 · Exploited in the wild
Exploited in the wild
Reported exploited in the wild
2026-11-09
Unverified 1 public PoC repository (listed below). Unverified: fake PoC repositories that carry malware are common.

Public exploits & proof-of-concept

Untrusted code · review only in an isolated lab
★ 0 · 2026-11-14

POC for CVE-2026-102895 + CVE-2026-102894 - authentication bypass pair in GPUStack: default loopback-source trust promotes unauthenticated requests to admin, plus unverified SAML callback takeover. KEV-listed. Vulnerable vs fixed controls included.

Remediation

What to do
Apply the vendor's fix or mitigation now. If none exists yet, restrict or disconnect the affected system until one does.
Exploitation confirmed
Nov 9, 2026
Ransomware use
Not known
Official CVE record

Intel updated 2026-11-16 16:05 UTC

Not sure whether this affects you?

Citadel's CTI team maps vulnerabilities like this one to your exposed systems and suppliers.

Talk to our CTI team