CVE-2026-5296 json
Missing Authorization in GitLab
published 2026-05-27 5 mo ago modified 2026-10-14 25 d ago also BIT-gitlab-2026-5296 , EUVD-2026-32619
- 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 9%
- public exploits
- 0
- none known
Summary
GitLab has remediated an issue in GitLab EE affecting all versions from 18.7 before 18.10.7, 18.11 before 18.11.4, and 19.0 before 19.0.1 that when foundational flows were enabled at the group level, could have allowed an authenticated user with developer-role permissions to bypass flow restrictions under certain conditions.
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
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 5 mo ago
Exploit prediction
0.20% chance of exploitation in the next 30 days, higher than 9% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- hackerone.com https://hackerone.com/reports/3626303 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:N/I:L/A:N |
| OSV | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | gitlab | >=18.7.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/3626303
technical-description, exploit, permissions-required, web
-
about.gitlab.com
/releases/2026/05/27/patch-release-gitlab-19-0-1-released/
release-notes, vendor-advisory, advisory
-
gitlab.com
/gitlab-org/gitlab/-/work_items/595423
broken-link, web
-
nvd.nist.gov
/vuln/detail/CVE-2026-5296
web
Sources
- CVE List CVE-2026-5296
- NVD CVE-2026-5296
- OSV BIT-gitlab-2026-5296
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.