CVE-2026-2601 json
Missing Authorization in GitLab
published 2026-05-27 5 mo ago modified 2026-10-14 25 d ago also BIT-gitlab-2026-2601 , EUVD-2026-32621
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 15%
- public exploits
- 0
- none known
Summary
GitLab has remediated an issue in GitLab EE affecting all versions from 11.5 before 18.10.7, 18.11 before 18.11.4, and 19.0 before 19.0.1 that under certain conditions could have allowed an authenticated user with developer-role permissions to access sensitive deployment data on projects due to improper authorization checks.
Patch / fix
- bitnami gitlab 18.10.7, 18.11.4, 19.0.2
- GitLab GitLab 18.10.7, 18.11.4, 19.0.1
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 5 mo ago
Exploit prediction
0.24% chance of exploitation in the next 30 days, higher than 15% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- hackerone.com https://hackerone.com/reports/3556381 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
| OSV | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | gitlab | >=11.5.0, <18.10.7 >=18.11.0, <18.11.4 >=19.0.0, <19.0.2 |
18.10.7 18.11.4 19.0.2 |
Affected products
- GitLab GitLab
Classification
- Weakness
-
- CWE-862 Missing Authorization
- Technology feeds
References
-
hackerone.com
/reports/3556381
technical-description, exploit, permissions-required, web
-
gitlab.com
/gitlab-org/gitlab/-/work_items/590389
broken-link, web
-
about.gitlab.com
/releases/2026/05/27/patch-release-gitlab-19-0-1-released/
release-notes, article
-
nvd.nist.gov
/vuln/detail/CVE-2026-2601
web
Sources
- CVE List CVE-2026-2601
- NVD CVE-2026-2601
- OSV BIT-gitlab-2026-2601
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.