Description
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.6 before 18.6.4, 18.7 before 18.7.2, and 18.8 before 18.8.2 that could have allowed an individual with existing knowledge of a victim's credential ID to bypass two-factor authentication by submitting forged device responses.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| GitLab | GitLab | 18.6 – < 18.6.4, 18.7 – < 18.7.2, 18.8 – < 18.8.2 | 18.6.4 |
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.8 +5 | No fix yet | — |
Advisories 2
- WID-SEC-2026-0178 GitLab: Mehrere Schwachstellen BSI CERT-Bund (WID) · Jan 22, 2026
- NCSC-2026-0037 Kwetsbaarheden verholpen in GitLab Community Edition en Enterprise Edition NCSC-NL (Netherlands) · Jan 22, 2026
References
- GitLab Issue #585333 issue-tracking permissions-required
- HackerOne Bug Bounty Report #3476052 technical-description exploit permissions-required
- https://about.gitlab.com/releases/2026/01/21/patch-release-gitlab-18-8-2-released/