App impersonation via improper authorization checks
Published Mar 29, 2026 · Updated Mar 29, 2026
Improper authorization in affected GitLab CE/EE releases allows remote authenticated users to obtain Jira Connect installation credentials. GitLab has not disclosed the affected endpoint or function, the mishandled parameters, or how the authorization check exposes those credentials. A Jira Connect installation and minimal workspace permissions are required; the credentials allow impersonation of the GitLab app.
Summary
What happened
Improper authorization in affected GitLab CE/EE releases allows remote authenticated users to obtain Jira Connect installation credentials. GitLab has not disclosed the affected endpoint or function, the mishandled parameters, or how the authorization check exposes those credentials. A Jira Connect installation and minimal workspace permissions are required; the credentials allow impersonation of the GitLab app.
The record
- CVE
- CVE-2026-2370
- Published
- Mar 29, 2026
- Updated
- Mar 29, 2026
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-233, T1528
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 29, 2026CVE publishedPublication date reported by the CVE source.
- Mar 29, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=14.3 <18.8.7
- Affected versionversion=18.10 <18.10.1
- Affected versionversion=18.9 <18.9.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo