Exploitation ongoing with high activity in latest observed window (1 mentions)
Recommended action window: Immediate (within 24h)
NVD description
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.
Priority
MEDIUM
Exploitation
ACTIVE
PoC
NONE
Patch
AVAILABLE
Momentum
STABLE
If you run products in this scope, you should treat this CVE as relevant to your environment.
| Date | Total | Labels |
|---|
| 2026-04-04 | 1 | Disclosure1 |
| 2026-04-23 | 1 | Patch1 |
GitLab's 2FA was bypassable for 3 weeks in January. If you self-host GitLab and didn't patch CVE-2026-0723, attackers could authenticate with just a password. https://stackshield.io/blog/gitlab-2fa-bypass-cve-2026-0723
Post summary
The tweet warns that GitLab’s CVE-2026-0723 2FA bypass was actively exploited in January; patching is required to prevent attackers from authenticating with just a password.
A GitLab 2FA bypass (CVE-2026-0723) was just disclosed. If you're self-hosting GitLab, this one matters. Here's what happened and what to do. https://stackshield.io/blog/gitlab-2fa-bypass-cve-2026-0723 #CyberSecurity
Post summary
The post announces the discovery of a new GitLab 2FA bypass vulnerability (CVE-2026-0723) and suggests remediation steps, but offers no PoC, exploit details, or active exploitation evidence.
2 of 2 entries
| Part | Vendor | Product | Version | Target SW | Target HW |
|---|---|---|---|---|---|
| App | gitlab | gitlab | - | - | - |
| App | gitlab | gitlab | - | - | - |