Description
GitLab has remediated an issue in GitLab EE affecting all versions from 13.9 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2 that under certain conditions could have allowed an authenticated user with Security Manager-role permissions to manage project security configuration even when the relevant feature was in a disabled state, due to incorrect authorization enforcement.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| GitLab | GitLab | 13.9 – < 18.10.8, 18.11 – < 18.11.5, 19.0 – < 19.0.2 | 18.10.8 |
Fixed in Linux distributions
Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.
Ubuntu
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Ubuntu 16.04 LTS | gitlab | No fix yet | — |
Wolfi
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Wolfi rolling | gitlab-runner-18.6 +35 | No fix yet | — |
| Wolfi rolling | gitlab-runner-19.0 +5 | 19.0.2-r0 | — |
Advisories 2
- NCSC-2026-0196 Kwetsbaarheden verholpen in GitLab Enterprise Edition NCSC-NL (Netherlands) · Jun 12, 2026
- WID-SEC-2026-1886 GitLab: Mehrere Schwachstellen BSI CERT-Bund (WID) · Jun 11, 2026
References
- https://gitlab.com/gitlab-org/gitlab/-/work_items/596656
- HackerOne Bug Bounty Report #3662615 technical-description exploit permissions-required
- https://about.gitlab.com/releases/2026/06/10/patch-release-gitlab-19-0-2-released/