GPU VulnDB

Database/Control plane, storage & DevOps

GitLab EE: a developer with group management permissions can escalate to broader system capabilities

CVSS 8.8CVE-2025-7691Control plane, storage & DevOpscurated

Impact

A user holding the Developer role plus specific group management permissions can escalate privileges and gain unauthorized access to additional system capabilities. On a fleet where GitLab drives CI into the cluster, extra privilege in GitLab generally converts into control over which pipelines run, with which runners and which credentials - the practical risk is a tenant developer reaching projects, runner configuration or CI variables that belong to other teams. The advisory does not enumerate which capabilities are gained; treat it as an in-application privilege boundary failure rather than host compromise. Affects GitLab EE from 16.6 before 18.2.7, 18.3 before 18.3.3, and 18.4 before 18.4.1.

Who can reach it

An authenticated GitLab EE user with the Developer role and certain group management permissions, over the network. Requires an existing account with that standing - not anonymous.

What to do

Upgrade GitLab EE to 18.2.7, 18.3.3 or 18.4.1 (or later) and restart the services. Until then, review who holds group management permissions alongside Developer in shared groups. Patching touches only the GitLab host.

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.