GPU VulnDB

Database/Control plane, storage & DevOps

GitLab workspaces: authenticated user can read Kubernetes Secrets from other namespaces via the agent

CVSS 7.6CVE-2026-97187Control plane, storage & DevOpscurated

Impact

Incorrect authorization in GitLab workspaces lets an authenticated user, under certain conditions, read Kubernetes Secrets from namespaces other than their own in clusters connected through the GitLab agent for Kubernetes. On a GPU cluster that uses GitLab for CI/CD or developer workspaces, those Secrets can hold registry credentials, storage keys, service-account tokens and other tenants' credentials, so one GitLab user can reach data belonging to other teams or namespaces. The advisory does not say exactly which conditions are required.

Who can reach it

Authenticated GitLab user with access to workspaces on an instance with a cluster connected through the GitLab agent for Kubernetes. The CVSS vector rates the privileges needed as high.

What to do

Upgrade GitLab CE/EE to 19.3.9, 19.4.8 or 19.5.6 (affected: 17.6 up to those versions). This is a GitLab server patch release with no change on GPU nodes. Consider rotating Secrets in namespaces that workspace users could reach through the agent.

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.