CVE-2026-0723 json
Unchecked Return Value in GitLab
published 2026-01-22 9 mo ago modified 2026-09-08 2 mo ago also BIT-gitlab-2026-0723 , EUVD-2026-4149
- cvss
- 7.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 64%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- bitnami gitlab 18.6.4, 18.7.2, 18.8.2
- GitLab GitLab 18.6.4, 18.7.2, 18.8.2
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 9 mo ago
Exploit prediction
1.04% chance of exploitation in the next 30 days, higher than 64% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- hackerone.com https://hackerone.com/reports/3476052 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.4 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N |
| OSV | 3.1 | 7.4 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | gitlab | >=18.6.0, <18.6.4 >=18.7.0, <18.7.2 >=18.8.0, <18.8.2 |
18.6.4 18.7.2 18.8.2 |
Affected products
- GitLab GitLab
Classification
- Weakness
-
- CWE-252 Unchecked Return Value
- Technology feeds
References
-
hackerone.com
/reports/3476052
technical-description, exploit, permissions-required, web
-
about.gitlab.com
/releases/2026/01/21/patch-release-gitlab-18-8-2-released/
release-notes, vendor-advisory, advisory
-
gitlab.com
/gitlab-org/gitlab/-/issues/585333
issue-tracking, permissions-required, broken-link, web
-
nvd.nist.gov
/vuln/detail/CVE-2026-0723
web
Sources
- CVE List CVE-2026-0723
- NVD CVE-2026-0723
- OSV BIT-gitlab-2026-0723
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.