GitLab Enterprise Edition up to 18.10.6/18.11.3/19.0.0 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 Enterprise Edition up to 18.10.6/18.11.3/19.0.0 and classified as problematic. Affected by this vulnerability is an unknown functionality. The manipulation leads to authorization. This vulnerability is traded as CVE-2026-2601. It is possible to initiate the attack remotely. There is no exploit available. The affected component should be upgraded.
Details
A vulnerability, which was classified as problematic, has been found in GitLab Enterprise Edition up to 18.10.6/18.11.3/19.0.0. This issue affects an unknown part. 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. The summary by CVE is:
GitLab has remediated an issue in GitLab EE affecting all versions from 11.5 before 18.10.7, 18.11 before 18.11.4, and 19.0 before 19.0.1 that under certain conditions could have allowed an authenticated user with developer-role permissions to access sensitive deployment data on projects due to improper authorization checks.
The weakness was shared by modhanami. The advisory is shared at hackerone.com. The identification of this vulnerability is CVE-2026-2601 since 02/16/2026. The exploitation is known to be easy. 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 317947 (Linux Distros Unpatched Vulnerability : CVE-2026-2601), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 18.10.7, 18.11.4 or 19.0.1 eliminates this vulnerability. The upgrade is hosted for download at about.gitlab.com.
The vulnerability is also documented in the databases at Tenable (317947) and EUVD (EUVD-2026-32621). 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: 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: 317947
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2026-2601
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Enterprise Edition 18.10.7/18.11.4/19.0.1
Timeline
02/16/2026 CVE reserved05/27/2026 Advisory disclosed
05/27/2026 VulDB entry created
06/01/2026 VulDB entry last update
Sources
Vendor: gitlab.comAdvisory: hackerone.com
Researcher: modhanami
Status: Confirmed
CVE: CVE-2026-2601 (🔒)
GCVE (CVE): GCVE-0-2026-2601
GCVE (VulDB): GCVE-100-366509
EUVD: 🔒
Entry
Created: 05/27/2026 21:59Updated: 06/01/2026 14:58
Changes: 05/27/2026 21:59 (65), 05/28/2026 00:36 (1), 06/01/2026 14:58 (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.