gpustack
Affected
- introduced
2.2.0, fixed2.2.2(ecosystem)
Fixed versions
2.2.2
Fix
- Fixed version
2.2.2pip install --upgrade gpustack==2.2.2
Advisory
Also known as: CVE-2026-103002
GPUStack: Missing authorization on several cluster and resource endpoints allows cross-user access and cluster takeover
Impact
An authenticated non-administrative user could access a Kubernetes cluster they are not authorized to access through GPUStack's Kubernetes API proxy.
The cluster_apiserver_proxy handler did not perform a resource-level authorization check before forwarding requests to the selected cluster. Requests were forwarded through a worker using its Kubernetes ServiceAccount credentials.
Depending on the permissions granted to that ServiceAccount, an attacker could read sensitive Kubernetes resources, create or modify workloads, or delete resources and disrupt services. Creating attacker-controlled workloads could result in code execution in the target cluster.
Exploitation requires a Kubernetes-provider cluster with a reachable worker. The operations available to the attacker are limited by the worker's ServiceAccount permissions.
Patches
Fixed in gpustack v2.2.2.
Workarounds
Restrict access to the GPUStack instance to trusted administrator accounts until upgrading.
High Basis: The source's own band: HIGH
2.2.0, fixed 2.2.2 (ecosystem)2.2.2
2.2.2pip install --upgrade gpustack==2.2.2Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0