Skip to main content
EPSS 0.4%top 64%

Improper Handling of Parameters in GitLab (CVE-2026-2370)

0
High
Published: 03/31/2026 (03/31/2026, 09:12:36 UTC)
Source: GCVE Database
Product: gitlab

Description

An authorization flaw in GitLab CE/EE versions from 14.3 up to but not including 18.8.7, 18.9 up to 18.9.3, and 18.10 up to 18.10.1 affects Jira Connect installations. This flaw allows an authenticated user with minimal workspace permissions to obtain installation credentials and impersonate the GitLab application. The issue has been remediated in the specified fixed versions.

Affected software

Bitnamimore threats →ghsa
gitlab
pkg:bitnami/gitlab
Affected versions
>=14.3.0 <18.8.7>=18.9.0 <18.9.3>=18.10.0 <18.10.1

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 09/10/2026, 23:02:34 UTC

Technical Analysis

CVE-2026-2370 is a vulnerability in GitLab CE/EE affecting Jira Connect installations where improper authorization checks allow an authenticated user with minimal workspace permissions to disclose installation credentials and impersonate the GitLab app. This vulnerability impacts versions >=14.3.0 <18.8.7, >=18.9.0 <18.9.3, and >=18.10.0 <18.10.1. The flaw was addressed by GitLab in releases 18.8.7, 18.9.3, and 18.10.1. The vulnerability has a high severity rating and a CVSS v3 base score around 8.1 to 8.8 depending on the source, reflecting high confidentiality and integrity impact with low attack complexity and privileges required.

Potential Impact

An attacker with minimal workspace permissions who is authenticated can exploit this vulnerability to obtain installation credentials for Jira Connect and impersonate the GitLab application. This could lead to unauthorized access and control over the GitLab app, potentially compromising confidentiality and integrity of the system. Availability impact is reported as none or low depending on scoring source.

Mitigation Recommendations

A fix is available and has been released in GitLab CE/EE versions 18.8.7, 18.9.3, and 18.10.1. Users should upgrade to these or later versions to remediate the vulnerability. Since this is not a cloud service, remediation depends on applying these patches. No additional mitigations are specified by the vendor advisory.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Gcve Source
db.gcve.eu
Osv Id
BIT-gitlab-2026-2370
Osv Schema Version
1.6.2
Aliases
["CVE-2026-2370"]
Ecosystems
["Bitnami"]
Database Specific Severity
High

Threat ID: 6a4c347c27e9c79719605e75

Added to database: 07/06/2026, 23:04:28 UTC

Last enriched: 09/10/2026, 23:02:34 UTC

Last updated: 09/10/2026, 23:02:34 UTC

Views: 74

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses