Skip to main content
Mallory
CriticalExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2026-102895: Unauthenticated Administrator Access in GPUStack

Published Nov 4, 2026 · Updated today
Trending this week#22of 428,812 vulnerabilities
Mention activity · 30 days115 mentions · peak 41 in a dayToday
CVSS9.8Critical · v3.1
EPSS0.52%45th percentile
CISA KEVYesAdded Nov 9, 2026
In the wildActivePer CISA KEV
Vendor
GPUStack
IdentifiersCVE-2026-102895CWE-287 · Improper Authentication

GPUStack versions before 2.2.0 contain an authentication bypass in get_current_user(). When force_auth_localhost is false, its default value, unauthenticated requests identified as originating from loopback automatically receive an administrator identity. The client_ip_getter logic can classify remote requests as local by accepting either a same-host reverse proxy's loopback peer address or a client-controlled X-GPUStack-Real-IP header. Successful exploitation enables administrative changes, persistent administrator API-key creation, disclosure of worker and cloud-provider secrets, and arbitrary code execution through custom inference backends. In-the-wild exploitation involving malicious backends running reverse shells was observed against GPUStack 2.1.1.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Remote unauthenticated attackers can compromise GPUStack control-plane confidentiality, integrity, and availability. Administrator access permits enumeration and modification of users, models, workers, and configuration; disclosure of worker registration tokens, cloud-provider credentials, and model-registry secrets; and creation of persistent administrator API keys usable independently of the original bypass. Malicious custom inference backends can execute operating-system commands on attached GPU workers, enabling further compromise of managed infrastructure.

Mitigation

If you can’t patch tonight, do this now.

Until upgrading, explicitly enable force_auth_localhost=true, such as through --force-auth-localhost, to require authentication for loopback requests. Restrict management API access to trusted networks through a VPN or authenticated access gateway. Strip client-supplied X-GPUStack-Real-IP headers at the edge and accept client-IP assertions only from trusted gateways. Header stripping alone is insufficient because a same-host reverse proxy forwarding over loopback can independently trigger the bypass.

Remediation

Patch, then assume compromise.

Upgrade GPUStack to version 2.2.0 or a later supported release. Version 2.2.0 removes automatic loopback-based administrator authentication and requires valid credentials regardless of request origin. The force_auth_localhost option becomes a deprecated no-op after this fix, so local automation previously relying on credential-free access must supply credentials. For potentially exposed deployments, investigate unauthorized users, API keys, model changes, and custom inference backends; revoke unauthorized access and rotate potentially exposed API keys, worker registration tokens, and cloud-provider or registry credentials. Patching alone does not remove attacker-created persistence.

Public exploits

Exploits

1 exploit validated by Mallory's analysis.

View more in app →
CVE-2026-102895-POCThe repository contains 15 files: two Python programs, Docker Compose and nginx configuration, nine evidence transcripts, a README, and an MIT license. The standalone, standard-library Python client poc.py implements two independent authentication-bypass modes. Loopback mode supports direct local access, a same-host reverse proxy, and a forged X-GPUStack-Real-IP header. SAML mode submits an unsigned response naming a chosen account and captures a gpustack_session cookie. Both workflows demonstrate administrative user enumeration and persistent API-key creation rather than merely detecting a version. No exploit framework, outbound command-and-control service, or executable reverse-shell payload is present in the supplied material. The lab provisions five GPUStack instances: vulnerable 2.1.2 default and gateway-disabled deployments, a 2.1.2 instance with --force-auth-localhost, and 2.2.0/2.2.2 controls, plus nginx. Host networking preserves the source-address behavior under test, but several services listen on all interfaces, so loopback-based captures do not mean the lab is exclusively loopback-bound. setup/lab-driver.py provides boot, stop, status, and readiness polling. The evidence reports loopback/header/proxy success on 2.1.2, rejection on 2.2.0, SAML success on 2.1.2 and 2.2.0, and rejection on unconfigured 2.2.2. SAML success against the hardened instance and 2.2.0 helps separate that primitive from the loopback bypass. Useful detection artifacts include X-GPUStack-Real-IP: 127.0.0.1, POST /auth/saml/callback, administrative requests to /v2/users and /v2/api-keys, the gpustack_session cookie, and API-key names beginning poc-cve-2026-102895-102894-. The evidence reports no useful application logging for the tested successful requests; proxy logs and key/account audits are therefore important. Repository guidance recommends upgrading to 2.2.2 or later; --force-auth-localhost addresses only the loopback path, while blocking the SAML callback and stripping untrusted real-IP headers are interim controls. Assessment is static: portions of README.md and poc.py were truncated, and neither execution nor independent verification of the CVE assignments, advisory claims, KEV listing, version ranges, or captured results was possible. The visible implementation and supplied transcripts are consistent with a functional exploit, with no apparent fake-exploit behavior. The original repository URL, git reference, and archive size were not supplied; empty strings and zero represent unavailable repository metadata.fixedbyreboot · Disclosed Nov 14, 2026 · python · network · web · localOperational
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GPUStackGpustackapplication
FAQ

Frequently asked questions

Is CVE-2026-102895 exploited in the wild?
Yes. As of Nov 17, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Nov 9, 2026.
Is there a public exploit for CVE-2026-102895?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2026-102895, the earliest disclosed Nov 14, 2026.
Is there a patch for CVE-2026-102895?
Upgrade GPUStack to version 2.2.0 or a later supported release. Version 2.2.0 removes automatic loopback-based administrator authentication and requires valid credentials regardless of request origin.
What products are affected by CVE-2026-102895?
Gpustack.
How severe is CVE-2026-102895?
CVE-2026-102895 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 0.52% (45th percentile) as of Nov 17, 2026.
Activity feed

Recent activity

115 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
cyberveilleNews · Nov 16, 2026🪲 Semaine 46 - CVE les plus discutées | CyberVeilleGPUStack before 2.2.0 can mistake remote requests for trusted loopback traffic under its default authentication configuration. This permits unauthenticated administrative access, secret disclosure, persistent administrator API-key creation, and code execution. Exploitation against version 2.1.1 is explicitly reported; version 2.2.0 fixes the issue.Read more ↗nuclei templates pull requestsNews · Nov 16, 2026Add [KEV] CVE-2026-102895.yaml - GPUStack < 2.2.0 - Authentication Bypass by buurosaaqi-dev · Pull Request #17860 · projectdiscovery/nuclei-templatesAn authentication bypass affecting GPUStack versions before 2.2.0. The supplied tests demonstrate that spoofing the X-GPUStack-Real-IP header as localhost allows an unauthenticated request to obtain the administrator identity in v2.1.1. Nuclei classifies the finding as critical. Upgrading to v2.2.0 or enabling --force-auth-localhost blocked the demonstrated bypass. Scanning and exploitation shown here are controlled local tests, not evidence of exploitation in the wild.Read more ↗cyberveilleNews · Nov 12, 2026Exploitation active de CVE-2026-102895 : contournement d'authentification dans GPUStack | CyberVeilleAn authentication bypass in GPUStack versions before 2.2.0. GPUStack trusts the X-Gpustack-Real-IP HTTP header without validation; setting it to 127.0.0.1 causes requests to be treated as trusted local traffic, bypassing authentication. The content reports active exploitation attempts against this GPU cluster management software used for AI workloads.Read more ↗malware newsNews · Nov 12, 2026Exploit Attempts for GPUStack Authentication Bypass (CVE-2026-102895), (Thu, Nov 12th) - Malware News - Malware Analysis, News and IndicatorsAn authentication-bypass vulnerability affecting GPUStack versions before 2.2.0, software used to manage GPU clusters for AI workloads. The content identifies version 2.2.0 as the fixed release and references an article reporting exploit attempts. It provides no technical details about those attempts.Read more ↗
+14 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity93Community discussion across Reddit, Mastodon, and other social sources.