Security readout for executives and security teams
Plain-English summary
CVE-2026-0723 is a GitLab CE/EE flaw that could let someone bypass two-factor authentication if they already know a victim’s credential ID. This threatens account takeover protections, but the published CVSS notes high attack complexity. GitLab says the issue is remediated in patch releases.
Executive priority
Treat as a high-priority GitLab patch if your organization runs affected versions. The business concern is weakening of 2FA for GitLab accounts, which can expose code and CI/CD assets. Prioritize internet-facing or high-value instances, while noting no confirmed active exploitation is cited.
Technical view
GitLab describes an unchecked return value issue, CWE-252, affecting GitLab CE/EE 18.6 before 18.6.4, 18.7 before 18.7.2, and 18.8 before 18.8.2. An attacker with existing knowledge of a victim credential ID could submit forged device responses to bypass 2FA. CVSS 3.1 score is 7.4, high.
Likely exposure
Organizations running self-managed GitLab CE/EE in the affected version ranges are the primary exposed population. The provided sources do not identify other affected products. Exposure is most relevant where 2FA protects sensitive repositories, CI/CD secrets, or administrative accounts.
Exploitation context
No CISA KEV listing is provided, and the source bundle does not state active exploitation. Public details indicate the attacker needs existing knowledge of a victim credential ID, raising complexity. Some referenced technical materials require permissions, limiting independent public verification.
Researcher notes
The public CVE record provides affected ranges, CVSS, CWE, and attack precondition. GitLab issue and HackerOne references are listed but permission-restricted in the source bundle, so public technical depth is limited. Avoid assuming exploit availability or broader impact beyond the stated 2FA bypass condition.
Mitigation direction
- Upgrade GitLab CE/EE 18.6 to 18.6.4 or later in that release line.
- Upgrade GitLab CE/EE 18.7 to 18.7.2 or later in that release line.
- Upgrade GitLab CE/EE 18.8 to 18.8.2 or later in that release line.
- Review GitLab’s patch release advisory for any environment-specific instructions.
- Prioritize instances protecting source code, CI/CD credentials, or privileged administrative access.
Validation and detection
- Inventory all GitLab CE/EE instances and record exact version numbers.
- Confirm no instance runs 18.6 before 18.6.4, 18.7 before 18.7.2, or 18.8 before 18.8.2.
- Verify the GitLab patch release was successfully applied.
- Review authentication logs for unusual successful 2FA events, noting no specific indicators were provided.
- Track vendor advisories for any newly published detection or remediation details.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-252: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-0723 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N2.25.2Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.4HighVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Source materials
- CVE List V5 sourceCVE List V5
- GitLab Issue #585333CVE reference · issue-tracking, permissions-required
- HackerOne Bug Bounty Report #3476052CVE reference · technical-description, exploit
- https://about.gitlab.com/releases/2026/01/21/patch-release-gitlab-18-8-2-released/CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Unchecked Return Value
Unchecked Return Value represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.