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.
CVE-2026-0723
HIGHNVD 7.4
7.4
- CVSS v3
- 7.4
- EG Score
- —
- EPSS
- —
- KEV
- Not listed
Published
January 22, 2026
Last Modified
January 26, 2026
References (3)
Vendor Advisories for CVE-2026-0723(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Frequently asked(4)
What is CVE-2026-0723?
CVE-2026-0723 is a high vulnerability published on January 22, 2026. 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…
When was CVE-2026-0723 disclosed?
CVE-2026-0723 was first published in the National Vulnerability Database on January 22, 2026, with the most recent update on January 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-0723?
CVE-2026-0723 has a CVSS v3 base score of 7.4 (NVD).
How do I remediate CVE-2026-0723?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-0723, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-0723
Is Your Infrastructure Affected by CVE-2026-0723?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.