GitLab Community Edition/Enterprise Edition up to 18.8.6/18.9.2/18.10.0 parameters
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.6 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in GitLab Community Edition and Enterprise Edition up to 18.8.6/18.9.2/18.10.0. The impacted element is an unknown function. Performing a manipulation results in improper handling of parameters. This vulnerability is identified as CVE-2026-2370. The attack can be initiated remotely. There is not any exploit available. It is suggested to upgrade the affected component.
Details
A vulnerability classified as critical has been found in GitLab Community Edition and Enterprise Edition up to 18.8.6/18.9.2/18.10.0. This affects an unknown code. The manipulation with an unknown input leads to a improper handling of parameters vulnerability. CWE is classifying the issue as CWE-233. The product does not properly handle when the expected number of parameters, fields, or arguments is not provided in input, or if those parameters are undefined. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 14.3 before 18.8.7, 18.9 before 18.9.3, and 18.10 before 18.10.1 affecting Jira Connect installations that could have allowed an authenticated user with minimal workspace permissions to obtain installation credentials and impersonate the GitLab app due to improper authorization checks.
The weakness was released by Maksyche. The advisory is shared at hackerone.com. This vulnerability is uniquely identified as CVE-2026-2370 since 02/11/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Neither technical details nor an exploit are publicly available.
The vulnerability scanner Nessus provides a plugin with the ID 304265 (GitLab 14.3 < 18.8.7 / 18.9 < 18.9.3 / 18.10 < 18.10.1 (CVE-2026-2370)), which helps to determine the existence of the flaw in a target environment.
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.
The vulnerability is also documented in the databases at Tenable (304265) and EUVD (EUVD-2026-17046). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
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: 7.7VulDB Meta Temp Score: 7.6
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 8.8
NVD Vector: 🔒
CNA Base Score: 8.1
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: Improper handling of parametersCWE: CWE-233 / CWE-229 / CWE-20
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: 304265
Nessus Name: GitLab 14.3 < 18.8.7 / 18.9 < 18.9.3 / 18.10 < 18.10.1 (CVE-2026-2370)
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/11/2026 CVE reserved03/30/2026 Advisory disclosed
03/30/2026 VulDB entry created
07/02/2026 VulDB entry last update
Sources
Vendor: gitlab.comAdvisory: hackerone.com
Researcher: Maksyche
Status: Confirmed
CVE: CVE-2026-2370 (🔒)
GCVE (CVE): GCVE-0-2026-2370
GCVE (VulDB): GCVE-100-354141
EUVD: 🔒
Entry
Created: 03/30/2026 07:31Updated: 07/02/2026 01:56
Changes: 03/30/2026 07:31 (65), 03/30/2026 09:09 (1), 03/30/2026 18:46 (2), 07/02/2026 01:56 (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.