Loading vulnerability…
CVE-2026-0723 is a high-severity authentication flaw in GitLab Community Edition and Enterprise Edition caused by an unchecked return value in authentication services. The issue affects GitLab CE/EE versions 18.6 before 18.6.4, 18.7 before 18.7.2, and 18.8 before 18.8.2. An attacker who already knows a victim's credential ID can submit forged device responses during the authentication flow and bypass two-factor authentication protections. Successful exploitation can result in unauthorized access to the targeted GitLab account.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
27 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Unknown
A critical authentication flaw in GitLab that allows bypass of two-factor authentication (2FA) due to an unchecked return value in authentication services, enabling forged device responses when the attacker knows the target account ID.
GitLab two-factor authentication bypass via forged device responses when an attacker already has valid user credentials.
A GitLab CE/EE vulnerability that could allow two-factor authentication bypass if an attacker knows a victim's credential ID and submits forged device responses.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.