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

Published Mar 29, 2026
·
Updated

GitLab has remediated an issue 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.

Other sources

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.

— MITRE

Affected Software

7 affected componentsFixes available
GitLab GitLab>=14.3<18.8.7, >=18.9<18.9.3, >=18.10<18.10.1
18.8.718.9.318.10.1
GitLab GitLab>=14.3.0<18.8.7
GitLab GitLab>=14.3.0<18.8.7
GitLab GitLab>=18.9.0<18.9.3
GitLab GitLab>=18.9.0<18.9.3
GitLab GitLab=18.10.0
GitLab GitLab=18.10.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 18.8.7Fixed in 18.9.3Fixed in 18.10.1
  2. Upgrade

    Upgrade GitLab CE/EE to a version that resolves this vulnerability.

    Fixed in 18.8.7
  3. Upgrade

    Upgrade GitLab CE/EE to a version that resolves this vulnerability.

    Fixed in 18.9.3
  4. Upgrade

    Upgrade GitLab CE/EE to a version that resolves this vulnerability.

    Fixed in 18.10.1

Event History

Mar 29, 2026
CVE Published
via MITRE·11:33 PM
Data Sourced
via MITRE·11:33 PM
RemedyDescriptionSeverityWeakness
Mar 30, 2026
Data Sourced
via Red Hat·12:01 AM
DescriptionSeverityAffected Software
Data Sourced
via NVD·12:16 AM
RemedyDescriptionSeverityWeaknessAffected Software
Apr 22, 2026
Data Sourced
via GitLab·07:54 AM
DescriptionSeverityAffected Software

Peer vulnerabilities

Found alongside the following vulnerabilities.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-2370?

CVE-2026-2370 has been classified with a medium severity as it involves improper handling of parameters that can lead to credential exposure.

2

How do I fix CVE-2026-2370?

To fix CVE-2026-2370, upgrade to the latest patched versions including GitLab 18.10.1 or later.

3

Who is affected by CVE-2026-2370?

CVE-2026-2370 affects GitLab CE/EE installations that are running versions prior to 18.10.1, 18.9.3, and 18.8.7.

4

What are the implications of CVE-2026-2370?

The implications of CVE-2026-2370 include the potential for an authenticated user to impersonate the GitLab installation and gain unauthorized access.

5

Is authentication required to exploit CVE-2026-2370?

Yes, an authenticated user with minimal workspace permissions may exploit CVE-2026-2370.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203