CVE-2026-0723
Gitlab 18.6.0 – 18.6.4
Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:NSummary
CVE-2026-0723 is a high-severity Unchecked Return Value (CWE-252) vulnerability in Gitlab Gitlab. Its CVSS base score is 7.4 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 46% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-0723 is a vulnerability in GitLab Community Edition (CE) and Enterprise Edition (EE) affecting all versions from 18.6 prior to 18.6.4, 18.7 prior to 18.7.2, and 18.8 prior to 18.8.2. The issue allows an attacker with prior knowledge of a victim's credential ID to bypass two-factor authentication (2FA) by submitting forged device responses. It is associated with CWE-252 (Unchecked Return Value) and carries a CVSS v3.1 base score of 7.4 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N).
An attacker can exploit this vulnerability remotely over the network without requiring user privileges or interaction, though it demands high attack complexity, likely due to the need for precise knowledge of the target's credential ID. Successful exploitation enables bypassing 2FA protections, potentially granting unauthorized access to the victim's GitLab account with high impacts on confidentiality and integrity, such as accessing sensitive repositories or project data.
GitLab has remediated the vulnerability, as detailed in their patch release notes for version 18.8.2 and related advisories. Security practitioners should upgrade affected GitLab CE/EE instances to version 18.6.4, 18.7.2, or 18.8.2 or later. Additional details are available in GitLab issue tracker entry 585333 and the corresponding HackerOne disclosure report 3476052.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-4149
Vulnerability Data
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…
more
by submitting forged device responses.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and code evaluation can discover instances where return values are ignored.
Requiring a documented development process and coding standards can mandate explicit checking of all function return values.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require checking and handling all function return values to detect error conditions.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development and acceptance can detect missing return-value checks.
Secure development life cycle mandates verification of return values to prevent undetected failures.
Application security requirements include input/output validation and error handling that covers return-value checks.
Secure system architecture and engineering principles require robust error handling and defensive coding practices.
Secure coding explicitly requires checking return values to avoid CWE-252.