CVE-2026-0723
BaseFortify
Publication date: 2026-01-22
Last updated on: 2026-01-26
Assigner: GitLab Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| gitlab | gitlab | From 18.6.0 (inc) to 18.6.4 (exc) |
| gitlab | gitlab | From 18.6.0 (inc) to 18.6.4 (exc) |
| gitlab | gitlab | From 18.7.0 (inc) to 18.7.2 (exc) |
| gitlab | gitlab | From 18.7.0 (inc) to 18.7.2 (exc) |
| gitlab | gitlab | From 18.8.0 (inc) to 18.8.2 (exc) |
| gitlab | gitlab | From 18.8.0 (inc) to 18.8.2 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-252 | The product does not check the return value from a method or function, which can prevent it from detecting unexpected states and conditions. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in GitLab CE/EE allows an attacker who already knows a victim's credential ID to bypass two-factor authentication by submitting forged device responses.
How can this vulnerability impact me? :
An attacker exploiting this vulnerability could bypass two-factor authentication, potentially gaining unauthorized access to user accounts and sensitive information.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, update GitLab CE/EE to versions 18.6.4, 18.7.2, 18.8.2 or later, as these versions contain the fix that prevents bypassing two-factor authentication by submitting forged device responses.