Owner-level token creation via missing role restriction
Published Feb 12, 2024 · Updated Jun 2, 2026
Privilege escalation in GitLab EE 16.8 through 16.8.1 allows remote authenticated users to create Owner-level group access tokens. The UI and REST API token-creation paths fail to restrict the requested token role to the custom role's Guest base role. A user assigned that custom Guest role with manage_group_access_tokens can obtain an Owner token and access group resources with Owner privileges.
Summary
What happened
Privilege escalation in GitLab EE 16.8 through 16.8.1 allows remote authenticated users to create Owner-level group access tokens. The UI and REST API token-creation paths fail to restrict the requested token role to the custom role's Guest base role. A user assigned that custom Guest role with manage_group_access_tokens can obtain an Owner token and access group resources with Owner privileges.
The record
- CVE
- CVE-2024-1250
- Published
- Feb 12, 2024
- Updated
- Jun 2, 2026
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-268, T1078
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 12, 2024CVE publishedPublication date reported by the CVE source.
- Jun 2, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=16.8 <16.8.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- GitLab issue 439175 reproduction procedureproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo