GitLab Community Edition/Enterprise Edition up to 17.11.3/18.0.1 authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.7 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in GitLab Community Edition and Enterprise Edition up to 17.11.3/18.0.1. This affects an unknown function. The manipulation leads to authorization. This vulnerability is documented as CVE-2025-5121. The attack can be initiated remotely. There is not any exploit available. It is suggested to upgrade the affected component.
Details
A vulnerability was found in GitLab Community Edition and Enterprise Edition up to 17.11.3/18.0.1. It has been rated as problematic. This issue affects an unknown code. The manipulation with an unknown input leads to a authorization vulnerability. Using CWE to declare the problem leads to CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
An issue has been discovered in GitLab CE/EE affecting all versions from 17.11 before 17.11.4 and 18.0 before 18.0.2. A missing authorization check may have allowed compliance frameworks to be applied to projects outside the compliance framework's group.
The weakness was released by jean_d-ou as 545429. The advisory is shared at gitlab.com. The identification of this vulnerability is CVE-2025-5121 since 05/23/2025. The exploitation is known to be difficult. The attack may be initiated remotely. Neither technical details nor an exploit are publicly available.
The vulnerability scanner Nessus provides a plugin with the ID 240212 (GitLab 17.11 < 17.11.4 / 18.0 < 18.0.2 (CVE-2025-5121)), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 17.11.4 or 18.0.2 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at Tenable (240212). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://gitlab.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.8VulDB Meta Temp Score: 7.7
VulDB Base Score: 5.0
VulDB Temp Score: 4.8
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 9.9
NVD Vector: 🔒
CNA Base Score: 8.5
CNA Vector (GitLab): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: AuthorizationCWE: CWE-862 / CWE-863 / CWE-285
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 240212
Nessus Name: GitLab 17.11 < 17.11.4 / 18.0 < 18.0.2 (CVE-2025-5121)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Community Edition/Enterprise Edition 17.11.4/18.0.2
Timeline
05/23/2025 CVE reserved06/20/2025 Advisory disclosed
06/20/2025 VulDB entry created
08/12/2025 VulDB entry last update
Sources
Vendor: gitlab.comAdvisory: 545429
Researcher: jean_d-ou
Status: Confirmed
CVE: CVE-2025-5121 (🔒)
GCVE (CVE): GCVE-0-2025-5121
GCVE (VulDB): GCVE-100-313541
Entry
Created: 06/20/2025 21:16Updated: 08/12/2025 17:15
Changes: 06/20/2025 21:16 (65), 06/21/2025 02:46 (2), 08/12/2025 17:15 (12)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.