dbcve.org
GitLabApplication

CVE-2026-2370

HIGH · 8.8 CVSS v3.1 Published 2026-03-30
Fix available
A fix is available. Upgrade to 18.8.7 / 18.9.3 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GitLabApplication
Affected:>= 14.3.0, < 18.8.7>= 18.9.0, < 18.9.3= 18.10.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 18.8.7 / 18.9.3 or later
Fixed in 18.8.718.9.3
Vendor patch about.gitlab.com →
Recommended fix High confidence

GitLab 18.10.1 or later (or 18.9.3+ if staying on 18.9, or 18.8.7+ if staying on 18.8)

  1. 1. Back up your GitLab instance data and configuration before proceeding with any upgrade.
  2. 2. Identify your current GitLab version by navigating to the GitLab administration area or running `gitlab-rake gitlab:env:info`.
  3. 3. Plan your upgrade path based on your current version - aim to upgrade to the latest stable release in your minor series or beyond the fixed versions.
  4. 4. For GitLab installations using the official GitLab packages (Omnibus), run `sudo apt-get update && sudo apt-get install gitlab-ce` (or `gitlab-ee` for Enterprise Edition) to upgrade to the latest available version.
  5. 5. For Docker installations, pull and run the latest image: `docker pull gitlab/gitlab-ee:latest` followed by recreating your container.
  6. 6. For source installations, follow the upgrade path in the GitLab documentation for upgrading from source.
  7. 7. After upgrade completes, verify the new version using `gitlab-rake gitlab:env:info`.
  8. 8. Test Jira Connect functionality to confirm the authorization fix is working correctly.
Caveat Upgrading across multiple minor versions may require reviewing the GitLab upgrade path documentation for any necessary intermediate upgrades; also review release notes for any configuration changes or deprecated features in the target version.

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2370 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-2370 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data