CVE-2026-102895

Summary

GPUStack versions prior to 2.2.0 allowed unauthenticated administrative access due to improper validation of request source IP in the get_current_user function, where a remote attacker could spoof the loopback address (127.0.0.1) via reverse proxy misconfiguration or a forged X-GPUStack-Real-IP header, bypassing authentication entirely.

Exploitability

Exploitation is straightforward for remote attackers with network access to the API endpoint, requiring only manipulation of the X-GPUStack-Real-IP header or exploitation of a same-host reverse proxy configuration.

Blast radius

Successful exploitation grants full administrative control, enabling creation of persistent credentials, theft of worker and cloud secrets, and remote code execution via the /v2/inference-backends/from-yaml endpoint.

Detection

Look for requests with X-GPUStack-Real-IP set to 127.0.0.1 or ::1 from non-loopback source IPs, especially when combined with administrative API calls (e.g., POST /v2/inference-backends/from-yaml, user/model creation endpoints) and absence of valid authentication tokens in the Authorization header.

Prioritized remediation

Upgrade to GPUStack version 2.2.0 or later, which fixes the IP validation flaw in get_current_user.

Analysis generated locally by garnet-coder (no data left the box). AI-assisted — verify against primary sources before acting.