Description
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 9.1 before 18.11.7, 19.0 before 19.0.4, and 19.1 before 19.1.2 that under certain conditions could have allowed an unauthenticated user to determine the existence of a private project due to improper authorization controls on cross-project reference pages.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| GitLab | GitLab | 9.1 – < 18.11.7, 19.0 – < 19.0.4, 19.1 – < 19.1.2 | 18.11.7 |
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-19.0 +11 | No fix yet | — |
| Wolfi rolling | gitlab-runner-19.1 +5 | 19.1.2-r0 | — |
Advisories 2
- NCSC-2026-0222 Kwetsbaarheden verholpen in GitLab Enterprise Edition en Community Edition NCSC-NL (Netherlands) · Jul 10, 2026
- WID-SEC-2026-2265 GitLab: Mehrere Schwachstellen BSI CERT-Bund (WID) · Jul 8, 2026
References
- HackerOne Bug Bounty Report #3704739 technical-description exploit permissions-required
- https://gitlab.com/gitlab-org/gitlab/-/work_items/597947
- https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-1-2-released/