GitLab Community Edition/Enterprise Edition up to 18.8.6/18.9.2/18.10.0 Repository authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.2 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as problematic has been discovered in GitLab Community Edition and Enterprise Edition up to 18.8.6/18.9.2/18.10.0. Affected is an unknown function of the component Repository Handler. Such manipulation leads to authorization. This vulnerability is documented as CVE-2026-2726. The attack can be executed remotely. There is not any exploit available. It is advisable to upgrade the affected component.
Details
A vulnerability, which was classified as problematic, has been found in GitLab Community Edition and Enterprise Edition up to 18.8.6/18.9.2/18.10.0. Affected by this issue is an unknown functionality of the component Repository Handler. The manipulation with an unknown input leads to a authorization vulnerability. Using CWE to declare the problem leads to CWE-863. The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions. Impacted is integrity. CVE summarizes:
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 11.10 before 18.8.7, 18.9 before 18.9.3, and 18.10 before 18.10.1 that could have allowed an authenticated user to perform unauthorized actions on merge requests in other projects due to improper access control during cross-repository operations.
The weakness was released by Pkkr. The advisory is shared for download at hackerone.com. This vulnerability is handled as CVE-2026-2726 since 02/18/2026. The exploitation is known to be easy. The attack may be launched remotely. There are neither technical details nor an exploit publicly available.
Upgrading to version 18.8.7, 18.9.3 or 18.10.1 eliminates this vulnerability. The upgrade is hosted for download at about.gitlab.com.
Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
Version
- 18.0
- 18.1
- 18.2
- 18.3
- 18.4
- 18.5
- 18.6
- 18.7
- 18.8
- 18.8.0
- 18.8.1
- 18.8.2
- 18.8.3
- 18.8.4
- 18.8.5
- 18.8.6
- 18.9
- 18.9.0
- 18.9.1
- 18.9.2
- 18.10.0
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-863 / 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 |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Community Edition/Enterprise Edition 18.8.7/18.9.3/18.10.1
Timeline
02/18/2026 CVE reserved03/25/2026 Advisory disclosed
03/25/2026 VulDB entry created
04/01/2026 VulDB entry last update
Sources
Vendor: gitlab.comAdvisory: hackerone.com
Researcher: Pkkr
Status: Confirmed
CVE: CVE-2026-2726 (🔒)
GCVE (CVE): GCVE-0-2026-2726
GCVE (VulDB): GCVE-100-353396
Entry
Created: 03/25/2026 20:01Updated: 04/01/2026 06:13
Changes: 03/25/2026 20:01 (66), 04/01/2026 06:13 (1)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.