GitLab Community Edition/Enterprise Edition up to 17.10.7/17.11.3/18.0.1 authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.2 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in GitLab Community Edition and Enterprise Edition up to 17.10.7/17.11.3/18.0.1 and classified as problematic. The impacted element is an unknown function. This manipulation causes authorization. This vulnerability is registered as CVE-2025-5195. Remote exploitation of the attack is possible. No exploit is available. The affected component should be upgraded.
Details
A vulnerability has been found in GitLab Community Edition and Enterprise Edition up to 17.10.7/17.11.3/18.0.1 and classified as problematic. Affected by this vulnerability is an unknown part. The manipulation with an unknown input leads to a authorization vulnerability. The CWE definition for the vulnerability is CWE-639. The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. As an impact it is known to affect confidentiality. The summary by CVE is:
An issue has been discovered in GitLab CE/EE affecting all versions from 17.9 before 17.10.7, 17.11 before 17.11.3, and 18.0 before 18.0.1. It was possible for authenticated users to access arbitrary compliance frameworks, leading to unauthorized data disclosure.
The advisory is shared at gitlab.com. This vulnerability is known as CVE-2025-5195 since 05/26/2025. The exploitation appears to be easy. The attack can be launched remotely. Neither technical details nor an exploit are publicly available.
The vulnerability scanner Nessus provides a plugin with the ID 238314 (GitLab 17.9 < 17.10.8 / 17.11 < 17.11.4 / 18.0 < 18.0.2 (CVE-2025-5195)), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 17.10.8, 17.11.4 or 18.0.2 eliminates this vulnerability.
The vulnerability is also documented in the databases at Tenable (238314) and EUVD (EUVD-2025-18172). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
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: 4.3VulDB Meta Temp Score: 4.2
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 4.3
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-639 / CWE-285 / CWE-266
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: 238314
Nessus Name: GitLab 17.9 < 17.10.8 / 17.11 < 17.11.4 / 18.0 < 18.0.2 (CVE-2025-5195)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Community Edition/Enterprise Edition 17.10.8/17.11.4/18.0.2
Timeline
05/26/2025 🔍06/12/2025 🔍
06/12/2025 🔍
08/09/2025 🔍
Sources
Vendor: gitlab.comAdvisory: 534960
Status: Confirmed
CVE: CVE-2025-5195 (🔍)
GCVE (CVE): GCVE-0-2025-5195
GCVE (VulDB): GCVE-100-312385
EUVD: 🔍
Entry
Created: 06/12/2025 14:12Updated: 08/09/2025 01:44
Changes: 06/12/2025 14:12 (64), 06/12/2025 14:54 (1), 06/12/2025 23:52 (2), 08/09/2025 01:44 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.