GPU VulnDB

Database/Control plane, storage & DevOps

GitLab: a limited-scope granular access token can authorize Kubernetes API proxy access beyond its scope

CVSS 4.9CVE-2026-18491Control plane, storage & DevOpscurated

Impact

In the GitLab agent for Kubernetes proxy-user flow, GitLab does not check the scope of a granular personal access token when it authorizes access to the Kubernetes API proxy. A user holding a token meant to be narrowly scoped can reach clusters connected through the GitLab agent beyond what the token was supposed to allow. The record does not say which Kubernetes actions become reachable. Where GPU clusters are managed through the GitLab agent, a leaked or delegated low-scope token is worth more than its owner intended. The scope change in the CVSS vector reflects the jump from GitLab into the connected cluster.

Who can reach it

An authenticated GitLab user holding a granular personal access token, against an instance with the Kubernetes agent proxy-user flow set up. Attack complexity is rated high ('under certain conditions'). Affects 19.2 and later.

What to do

Upgrade GitLab to 19.3.9, 19.4.8 or 19.5.6. Self-managed instances need a GitLab upgrade and service restart. Until then, check which granular tokens can reach agent-connected clusters and revoke the ones nobody needs.

References

Related entries

All Control plane, storage & DevOps entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.