GitLab Enterprise Edition up to 18.4.4/18.5.2/18.6.0 direct request
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.2 | $0-$5k | 0.00 |
Summary
A vulnerability was found in GitLab Enterprise Edition up to 18.4.4/18.5.2/18.6.0. It has been rated as problematic. The affected element is an unknown function. Performing a manipulation results in direct request. This vulnerability is cataloged as CVE-2025-6195. It is possible to initiate the attack remotely. There is no exploit available. Upgrading the affected component is advised.
Details
A vulnerability, which was classified as problematic, was found in GitLab Enterprise Edition up to 18.4.4/18.5.2/18.6.0. This affects an unknown function. The manipulation with an unknown input leads to a direct request vulnerability. CWE is classifying the issue as CWE-425. The web application does not adequately enforce appropriate authorization on all restricted URLs, scripts, or files. This is going to have an impact on confidentiality. The summary by CVE is:
GitLab has remediated an issue in GitLab EE affecting all versions from 13.7 before 18.4.5, 18.5 before 18.5.3, and 18.6 before 18.6.1 that could have allowed an authenticated user to view information from security reports under certain configuration conditions.
The weakness was shared by mateuszek as 549937. The advisory is shared at gitlab.com. This vulnerability is uniquely identified as CVE-2025-6195 since 06/17/2025. The exploitability is told to be easy. It is possible to initiate the attack remotely. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1006 for this issue.
The vulnerability scanner Nessus provides a plugin with the ID 298853 (GitLab 13.7 < 18.4.5 / 18.5 < 18.5.3 / 18.6 < 18.6.1 (CVE-2025-6195)), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 18.4.5, 18.5.3 or 18.6.1 eliminates this vulnerability.
The vulnerability is also documented in the databases at Tenable (298853) and EUVD (EUVD-2025-199757). 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: 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: Direct requestCWE: CWE-425
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: 298853
Nessus Name: GitLab 13.7 < 18.4.5 / 18.5 < 18.5.3 / 18.6 < 18.6.1 (CVE-2025-6195)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Enterprise Edition 18.4.5/18.5.3/18.6.1
Timeline
06/17/2025 CVE reserved11/27/2025 Advisory disclosed
11/27/2025 VulDB entry created
02/13/2026 VulDB entry last update
Sources
Vendor: gitlab.comAdvisory: 549937
Researcher: mateuszek
Status: Confirmed
CVE: CVE-2025-6195 (🔒)
GCVE (CVE): GCVE-0-2025-6195
GCVE (VulDB): GCVE-100-333669
EUVD: 🔒
Entry
Created: 11/27/2025 03:23Updated: 02/13/2026 14:33
Changes: 11/27/2025 03:23 (66), 11/29/2025 02:19 (1), 02/13/2026 14:33 (2)
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.