Security readout for executives and security teams
Plain-English summary
This GitLab issue could let a low-privileged authenticated user in a Jira Connect workspace obtain installation credentials and act as the GitLab app. That creates serious confidentiality and integrity risk for affected integrations, but the provided sources do not show confirmed active exploitation.
Executive priority
Treat this as a high-priority patching item for GitLab environments using Jira Connect. The business risk is unauthorized access to integration credentials and app impersonation, which may affect connected workflows and data integrity.
Technical view
CVE-2026-2370 is an improper authorization/parameter-handling issue in GitLab CE/EE affecting Jira Connect installations. A network-accessible authenticated user with minimal workspace permissions could obtain installation credentials and impersonate the GitLab app. GitLab remediated affected ranges before 18.8.7, 18.9.3, and 18.10.1.
Likely exposure
Exposure is most likely on self-managed GitLab CE/EE instances running affected versions and using Jira Connect installations. Instances without Jira Connect evidence are lower priority, but version inventory should still confirm status.
Exploitation context
The CVSS vector indicates network access, low attack complexity, low privileges, and no user interaction. The bundle includes a HackerOne report tagged for exploit and permissions-required, but KEV is false and no cited source confirms exploitation in the wild.
Researcher notes
Focus validation on authorization boundaries around Jira Connect installation credentials. Evidence supports authenticated, low-privilege access and high confidentiality/integrity impact. Do not assume broader GitLab compromise or active exploitation without additional source evidence.
Mitigation direction
- Upgrade affected GitLab CE/EE instances to 18.8.7, 18.9.3, 18.10.1, or later.
- Prioritize GitLab instances with Jira Connect installations.
- Review GitLab’s patch release advisory for version-specific guidance.
- Assess whether exposed installation credentials require rotation under vendor guidance.
- Limit Jira Connect workspace permissions where operationally feasible.
Validation and detection
- Inventory GitLab CE/EE versions against the affected ranges.
- Identify whether Jira Connect installations are configured.
- Confirm upgraded instances report fixed versions or later supported releases.
- Review integration and audit logs for unusual GitLab app impersonation activity.
- Document whether credential rotation was required or completed.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-233: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-2370 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N2.85.2GitLabCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N2.85.2redhat-SADPVulnerability scoring details
Base CVSS 3.1 score
8.1HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Base CVSS 3.1 score
8.1HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- ADP timelineredhat-SADP
Made public.
- CVE publishedCVE Program
The CVE record was published.
- ADP timelineredhat-SADP
Reported to Red Hat.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
- 2026-03-30T00:01:16.632Z: Reported to Red Hat.
- 2026-03-29T23:33:44.410Z: Made public.
Source materials
- CVE List V5 sourceCVE List V5
- HackerOne Bug Bounty Report #3522829CVE reference, GitLab · technical-description, exploit
- https://gitlab.com/gitlab-org/gitlab/-/work_items/589635CVE reference, GitLab
- https://about.gitlab.com/releases/2026/03/25/patch-release-gitlab-18-10-1-released/CVE reference, GitLab
- https://access.redhat.com/security/cve/CVE-2026-2370CVE reference, redhat-SADP · vdb-entry, x_refsource_REDHAT
- RHBZ#2452920CVE reference, redhat-SADP · issue-tracking, x_refsource_REDHAT
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-2370.jsonCVE reference, redhat-SADP · x_sadp-csaf-vex
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Handling of Parameters
Improper Handling of Parameters represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.