CVE-2026-2370VulnerabilityPublished 31 Mar 2026Updated 10 Sep 2026

CVE-2026-2370: GitLab · Improper Handling of Parameters

Affects gitlabSource GCVE Database

Not known to be exploited · fixed in 18.10.1 : patch gitlab soon.

Data as of 26 Oct 2026, 06:26 UTC

Severity

High

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 18.10.1, 18.9.3, 18.8.7

Exploitation evidence

Disclosed: evidence found.
CVE published 31 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade gitlab to 18.10.1, 18.9.3 or 18.8.7.

Affected software

Product	Affected	Fixed in
Bitnamigitlab`pkg:bitnami/gitlab`Other threats	Affected >=14.3.0 <18.8.7 >=18.9.0 <18.9.3 >=18.10.0 <18.10.1	Fixed in 18.8.7 18.9.3 18.10.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

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.

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.

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.

References

Community reviews

Loading reviews…