A critical security vulnerability identified as CVE-2026-102895 has been disclosed in GPUStack, carrying a CVSS v3.1 severity rating of 9.8 (CRITICAL). The flaw is confirmed under active exploitation by threat actors and has been added to CISA's Known Exploited Vulnerabilities catalog (added 2026-11-09), requiring emergency defensive mobilization.

Specification Parameter Vulnerability Detail & Telemetry Technical Risk & Exploit Impact
Target Software & Vendor GPUStack (GPUStack) Enterprise infrastructure component and core runtime dependencies.
Vulnerability Identifier CVE-2026-102895 Primary tracking ID cataloged across NIST NVD and vendor PSIRT.
Weakness Taxonomy CWE-287: Authentication Bypass Improper boundary validation and runtime authorization enforcement.
CVSS v3.1 Metrics 9.8 (CRITICAL) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Remote exploitable attack vector requiring zero elevated user privileges.
Remediation Baseline Version 2.2.0 and later Immediate vendor update and network ingress micro-segmentation.

Executive Threat Summary & Architectural Context

GPUStack serves as an enterprise infrastructure component across production networks. Vulnerabilities within this technology stack present severe risks, enabling adversaries to compromise data confidentiality, subvert cryptographic guarantees, or disable core services.

Vulnerability Mechanics & Technical Root Cause (CWE-287 — Authentication Bypass)

Official technical advisories from NIST NVD and primary vendor telemetry describe the underlying defect as follows:

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.

The root cause resides in improper state validation and boundary enforcement inside the component's request processing pipeline:

/* Representative Protocol Request Exploiting CVE-2026-102895 */
POST /api/v2/action/dispatch HTTP/1.1
Host: secure-endpoint.internal.enterprise
User-Agent: CST-Telemetry-Audit/2.0
Content-Type: application/json
Accept: application/json
Authorization: Bearer [REDACTED_SESSION_TOKEN]

{
  "transaction_id": "tx-exploit-cve-2026-102895",
  "routing_target": "internal_engine_subsystem",
  "payload_parameters": {
    "filter_expression": "1' OR '1'='1",
    "command_override": "; /bin/sh -c 'id; uname -a > /tmp/cst_audit_proof'",
    "debug_mode": true
  }
}

Step-by-Step Remediation Playbook & Patch Commands

Enterprise administrators must execute the following remediation checklist immediately:

  1. Apply Official Vendor Updates: Upgrade installed packages to Version 2.2.0 and later: 
    # For Debian / Ubuntu systems:
sudo apt-get update && sudo apt-get install --only-upgrade gpustack -y

# For containerized microservices:
docker pull gpustack:latest
docker-compose up -d --force-recreate
  2. Network Ingress Filtering: Isolate management interfaces behind an enterprise VPN or zero-trust network access (ZTNA) gateway.