Unintended Proxy or Intermediary ('Confused Deputy') in GitLab
Summary
| CVE | CVE-2026-3160 |
|---|---|
| State | PUBLISHED |
| Assigner | GitLab |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-05-14 06:16:22 UTC |
| Updated | 2026-05-14 06:16:22 UTC |
| Description | GitLab has remediated an issue in GitLab CE/EE affecting all versions from 13.7 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3 that could have allowed an authenticated user to view Jira issues outside the configured project scope due to an integration filter functioning only as a display control rather than enforcing access boundaries as specified. |
Risk And Classification
Primary CVSS: v3.1 5.8 MEDIUM from [email protected]
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N
Problem Types: CWE-441 | CWE-441 CWE-441: Unintended Proxy or Intermediary ('Confused Deputy')
| Version | Source | Type | Score | Severity | Vector |
|---|---|---|---|---|---|
| 3.1 | [email protected] | Secondary | 5.8 | MEDIUM | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N |
| 3.1 | CNA | CVSS | 5.8 | MEDIUM | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N |
CVSS v3.1 Breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N
Vendor Declared Affected Products
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| gitlab.com/gitlab-org/gitlab/-/work_items/591354 | [email protected] | gitlab.com | |
| hackerone.com/reports/3566042 | [email protected] | hackerone.com | |
| about.gitlab.com/releases/2026/05/13/patch-release-gitlab-18-11-3-released | [email protected] | about.gitlab.com | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
Vendor Comments And Credit
Discovery Credit
CNA: Thanks [maksyche](https://hackerone.com/maksyche) for reporting this vulnerability through our HackerOne bug bounty program (en)
Additional Advisory Data
Solutions
CNA: Upgrade to versions 18.9.7, 18.10.6, 18.11.3 or above. Additionally, review the Jira API token used in your integration and ensure it is scoped to only the Jira projects you intend to expose. The project keys field in the integration configuration filters the displayed issues but does not restrict the token's access. To limit which issues can be read through the integration, generate the API token from a Jira account with access only to the desired projects.