CVE-2026-102895: GPUStack flaw exploited in the wild, what we know

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.

• Severity: CRITICAL (CVSS 3.1 9.8, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).
• Weakness: CWE-287, CWE-290, CWE-346.
• NVD published 2026-11-04, status Analyzed.

Anyone running GPUStack in the version ranges below. Internet-facing instances are the priority.

• gpustack gpustack: up to (not including) 2.2.0.

Version ranges come from the NVD CPE configuration. Confirm against the vendor advisory before you rely on them.

• Exploited in the wild: added to the CISA Known Exploited Vulnerabilities catalog on 2026-11-09; federal remediation due date 2026-11-12.

CISA added CVE-2026-102895 to its Known Exploited Vulnerabilities catalog on 2026-11-09. A KEV listing means CISA has evidence that attackers are using the flaw against real systems, not just that it could be used.

If your business runs GPUStack, put this at the top of the patch list. CISA gave US federal agencies until 2026-11-12 to deal with it, and that is a sensible deadline for a small business too.

• Patch. Update to a fixed release: gpustack gpustack 2.2.0 or later. These versions come from NVD's configuration data, so confirm them against the advisory from GPUStack.
• If you cannot patch yet. Follow CISA's 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.
• Check your exposure. Find out whether GPUStack can be reached from the internet, for example a VPN portal, an admin login page or a file-transfer site. Your firewall's port-forwarding rules and your IT provider's list of public-facing systems are the quickest places to look. Exposed copies come first.
• When to call IT support. Call your IT support provider now if you run GPUStack and cannot confirm it is updated, if it was reachable from the internet before you patched it, or if you notice accounts, sign-ins or files you do not recognise. The last two can mean the system was already hit, and checking that properly takes someone who can read the logs.

• EPSS (probability of exploitation activity in the next 30 days): 0.33%, higher than 26% of all scored CVEs (as of 2026-11-09).
• CVERadar threat level: 64/100 (see methodology).
• Likely ATT&CK techniques: T1190 Exploit Public-Facing Application (inferred); T1078 Valid Accounts (inferred).

1. Find every instance. List where GPUStack runs, including test, DR and forgotten internet-facing systems, and record the installed version.
2. Upgrade to a fixed release. gpustack gpustack: 2.2.0 or later. Get the build from the vendor advisory.
3. If you can't patch today, follow CISA's 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.
4. Verify the fix. Re-run the version check on every instance and confirm it reports the fixed build (2.2.0 or later). Re-scan from outside if the service is exposed.
5. Hunt for signs of earlier compromise. If the system was exposed before you patched, assume it may have been hit and check the items below.
6. Rotate credentials stored on or used by the affected system if you cannot rule out compromise, and keep the logs you reviewed.

Detection hints

• T1190 Exploit Public-Facing Application: Review WAF, reverse-proxy and application logs for unusual requests to GPUStack (odd paths, oversized or encoded payloads, bursts of errors), going back to at least 2026-11-04.
• T1078 Valid Accounts: Check for logins from new sources or accounts you did not create.

Detection commands are generic starting points, not CVE-specific signatures. Use the indicators from the vendor advisory when it publishes them.

• NVD: CVE-2026-102895 nvd.nist.gov/vuln/detail/CVE-2026-102895
• CVE.org record www.cve.org/CVERecord?id=CVE-2026-102895
• Vendor link from CISA KEV github.com/gpustack/gpustack/security/advisories/GHSA-gj9m-f8ph-pmhr
• Patch github.com/gpustack/gpustack/commit/53f42a6a553542974396d16a4ff6b12bcb
• Patch github.com/gpustack/gpustack/pull/5346
• Release Notes github.com/gpustack/gpustack/releases/tag/v2.2.0
• CISA KEV catalog www.cisa.gov/known-exploited-vulnerabilities-catalog
• FIRST EPSS (2026-11-09) api.first.org/data/v1/epss?cve=CVE-2026-102895