Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
High

Improper authorization in GitLab Jira Connect installations allows app impersonation

IdentifiersCVE-2026-2370CWE-233· Improper Handling of Parameters

CVE-2026-2370 is an improper authorization vulnerability in GitLab CE/EE affecting Jira Connect installations. It impacts all versions from 14.3 before 18.8.7, 18.9 before 18.9.3, and 18.10 before 18.10.1. Due to insufficient authorization checks, an authenticated user with only minimal workspace permissions can obtain Jira Connect installation credentials. With those credentials, the attacker can impersonate the GitLab application in the Jira integration context and access data exposed through that trust relationship.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows a low-privileged authenticated user to extract installation credentials for the Jira Connect integration and impersonate the GitLab app. This can result in unauthorized access to integrated Jira data and unauthorized actions performed as the application, with high confidentiality and integrity impact. No direct availability impact is indicated in the provided information.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure by disabling or removing affected Jira Connect integrations where feasible, limiting which users have workspace access, and reviewing permissions for accounts with even minimal workspace roles. Monitor for suspicious access to Jira Connect installation data, unexpected use of GitLab app credentials, and anomalous activity involving the GitLab-Jira integration. These are temporary risk-reduction measures; upgrading to a fixed version is the primary mitigation.

Remediation

Patch, then assume compromise.

Upgrade GitLab CE/EE to a fixed release: 18.8.7 or later in the 18.8 series, 18.9.3 or later in the 18.9 series, or 18.10.1 or later in the 18.10 series. Versions from 14.3 up to but excluding those patched releases are affected. GitLab has remediated the improper authorization issue in these releases.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GitLabGitlabapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity8

Community discussion across Reddit, Mastodon, and other social sources.