CVE-2026-2370
Gitlab 14.3.0 – 18.8.7
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:NSummary
CVE-2026-2370 is a high-severity Improper Handling of Parameters (CWE-233) vulnerability in Gitlab Gitlab. Its CVSS base score is 8.1 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 36th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-2370 is a vulnerability in GitLab Community Edition (CE) and Enterprise Edition (EE), affecting all versions from 14.3 prior to 18.8.7, 18.9 prior to 18.9.3, and 18.10 prior to 18.10.1. The flaw impacts Jira Connect installations due to improper authorization checks (CWE-233), which allow an authenticated user with minimal workspace permissions to obtain installation credentials and impersonate the GitLab application.
An authenticated attacker with minimal workspace permissions can exploit this issue remotely over the network (AV:N) with low attack complexity (AC:L), requiring no user interaction (UI:N) and maintaining unchanged scope (S:U). Exploitation yields high confidentiality (C:H) and integrity (I:H) impacts with no availability effects (A:N), as indicated by the CVSS v3.1 base score of 8.1, enabling the attacker to access sensitive credentials and act as the GitLab app.
GitLab has remediated the vulnerability through patches, including the release of GitLab 18.10.1. Further details on the fix and issue tracking are provided in the GitLab patch release notes at https://about.gitlab.com/releases/2026/03/25/patch-release-gitlab-18-10-1-released/, the internal work item at https://gitlab.com/gitlab-org/gitlab/-/work_items/589635, and the HackerOne disclosure report at https://hackerone.com/reports/3522829.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-17046
Vulnerability Data
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…
more
credentials and impersonate the GitLab app due to improper authorization checks.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
SI-10 requires validity checks on information inputs, directly stopping missing or undefined parameters from being accepted.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require input validation and correct parameter handling to avoid this weakness.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect missing-parameter issues but does not prevent them at design time.
Secure development lifecycle includes input validation and parameter handling requirements that reduce improper parameter handling.
Application security requirements explicitly call for validation of inputs and parameters, mitigating missing or undefined arguments.
Secure coding standards directly address proper handling of function parameters and input validation.