Disclosed weakness · no CVE recorded

GPUStack cluster proxy could grant management access to ordinary members

GPUStack · GPUStack

First documented disclosure · Review checkpoint

Summary

An ordinary member of a cluster-owning organization could perform Kubernetes management operations beyond their assigned role.

Severity and exploitation evidence

High · 8.8/10 · CVSS 3.1. Severity source.

Exploitation not established: The original source establishes the weakness but does not report malicious exploitation.

Exploitation evidence source

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

The Kubernetes proxy checked which organization owned a cluster but did not enforce the individual member’s management role.

Conditions required

A non-owner member belongs to the organization that owns a Kubernetes cluster and a proxying worker is reachable.

Potential impact

The caller could exceed read-only workload permissions; the worker’s Kubernetes permissions bound the impact.

Affected versions and configurations

>= 2.2.2, <= 2.3.0

Fix and mitigation status

2.3.1 fixes this issue.

Practical next steps

Upgrade to 2.3.1 or a later release containing this fix. Audit cluster changes, restrict management access and limit worker service-account permissions.

Operating lesson

Test both membership and role when proxying cluster management operations.

Evidence and limits

The maintainer assigns the score. No CVE was listed in the original advisory at review. GPUStack distinguishes this issue from the earlier CVE-2026-103002.

Sources