Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.8amended

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

CVE-2026-103002GHSA-3hch-x692-6qj3

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (gpustack 2.2.2), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • PyPI gpustack

    Affected
    >= 2.2.0, < 2.2.2
    Fixed in
    2.2.2

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.8 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
  • CVE-2026-103002: 0.36% estimated exploitation activity in the next 30 days; percentile 30.10 (FIRST EPSS, 2026-11-10). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from osv record GHSA-3hch-x692-6qj3

  2. Revision 1 · created ·

    Published from ghsa record GHSA-3hch-x692-6qj3

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-103002

Advisory: GPUStack: Missing authorization on several cluster and resource endpoints allows cross-user access and cluster takeover
IDs: CVE-2026-103002, GHSA-3hch-x692-6qj3
Record: https://patchnext.com/advisories/cve-2026-103002 (revision 2, source checked 11 Nov 2026, 07:05 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: gpustack 2.2.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI gpustack: affected >= 2.2.0, < 2.2.2; fixed in 2.2.2

## Suggested inspection (read-only)
- `python -m pip show gpustack`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on gpustack.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-3hch-x692-6qj3 (GitHub-reviewed advisory GHSA-3hch-x692-6qj3 lists affected ranges: PyPI gpustack >=2.2.0 <2.2.2)
- Verified: https://osv.dev/vulnerability/GHSA-3hch-x692-6qj3 (OSV record GHSA-3hch-x692-6qj3 lists affected ranges: PyPI gpustack >=2.2.0 <2.2.2 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…