CVE-2026-0723

Unknown Unknown - Not Provided

BaseFortify

Publication date: 2026-01-22

Last updated on: 2026-01-26

Assigner: GitLab Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-01-22

Last Modified

2026-01-26

Generated

2026-07-06

AI Q&A

2026-01-22

EPSS Evaluated

2026-07-05

NVD

CVE-2026-0723

EUVD

EUVD-2026-4149

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

KEV

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

Executive Summary

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.

Impact Analysis

An attacker exploiting this vulnerability could bypass two-factor authentication, potentially gaining unauthorized access to user accounts and sensitive information.

Mitigation Strategies

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.

Hi! I’m here to help you understand CVE-2026-0723. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70