Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
High

GitLab CE/EE Two-Factor Authentication Bypass via Forged Device Responses

IdentifiersCVE-2026-0723CWE-252· Unchecked Return Value

CVE-2026-0723 is a high-severity vulnerability in GitLab Community Edition (CE) and Enterprise Edition (EE) authentication services, affecting versions 18.6 before 18.6.4, 18.7 before 18.7.2, and 18.8 before 18.8.2. The flaw is described as an unchecked return value issue in the authentication flow. Under the documented conditions, an attacker who already knows a victim's credential ID can submit forged device responses and bypass two-factor authentication (2FA). The issue impacts GitLab's device-based authentication handling and can result in unauthorized authentication despite 2FA protections being enabled.

Share:
For your environment

Are you exposed to this one?

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.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows bypass of 2FA protections for targeted GitLab accounts. This can lead to unauthorized account access and account takeover, with consequent exposure or manipulation of data accessible to the compromised user, including repositories, CI/CD data, project information, and other sensitive content permitted by that account. Available scoring information indicates high confidentiality and integrity impact, with no direct availability impact.

Mitigation

If you can’t patch tonight, do this now.

No vendor workaround is specifically documented in the provided content. Where immediate patching is not possible, reduce exposure by closely monitoring authentication events for anomalous login behavior, restricting administrative and user access paths where feasible (for example via VPN or IP allowlists), and minimizing exposure of credential IDs through logs, integrations, or other externalized metadata. These measures are compensating controls only and do not eliminate the vulnerability.

Remediation

Patch, then assume compromise.

Upgrade GitLab CE/EE to a fixed release: 18.6.4 or later for the 18.6 branch, 18.7.2 or later for the 18.7 branch, or 18.8.2 or later for the 18.8 branch. GitLab advised self-managed installations to upgrade immediately. GitLab.com is already patched, and GitLab Dedicated customers reportedly do not need to take action.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GitLabGitlabapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity17

Community discussion across Reddit, Mastodon, and other social sources.