Privilege Chaining in GitLab

published 2024-02-12 2 y ago modified 2026-06-17 4 mo ago also BIT-gitlab-2024-1250 , EUVD-2024-17011

cvss: 6.5; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.5%; EPSS 0.5% chance of exploitation in 30 days, percentile 45%
public exploits: 0; none known

An issue has been discovered in GitLab EE affecting all versions starting from 16.8 before 16.8.2. When a user is assigned a custom role with manage_group_access_tokens permission, they may be able to create group access tokens with Owner privileges, which may lead to privilege escalation.

Patch / fix

fixed in 2

bitnami gitlab 16.8.2
GitLab GitLab 16.8.2

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: total
Assessed: 2 y ago (2024-02-13)

Exploit prediction

0.54% chance of exploitation in the next 30 days, higher than 45% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	6.5	CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N
NVD	3.1	6.5	CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N
OSV	3.1	6.5	CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N

Affected packages

ecosystem	package	affected	fixed in
bitnami	gitlab	>=16.8.0, <16.8.2	16.8.2

Affected products

GitLab GitLab

Classification

Weakness

CWE-268 Privilege Chaining

Technology feeds

GitLab rss critical rss

References

gitlab.com /gitlab-org/gitlab/-/issues/439175
issue-tracking, permissions-required, web
nvd.nist.gov /vuln/detail/CVE-2024-1250
web

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Enhance with deb and rpm package type records.

Summary