GitLab Security Flaws Two-Factor Authentication Bypass DoS
GitLab has released critical security patches addressing multiple vulnerabilities affecting both Community Edition (CE) and Enterprise Edition (EE).
Versions 18.8.2, 18.7.2, and 18.6.4 are now available to fix flaws that enable two-factor authentication bypass and denial-of-service attacks.
GitLab strongly recommends that all self-managed installations upgrade immediately, while GitLab.com has already deployed the patches.
The most severe flaw, tracked as CVE-2026-0723, is an unchecked return value issue in authentication services that allows attackers with knowledge of a victim’s credential ID to bypass two-factor authentication by submitting forged device responses.
This high-severity vulnerability (CVSS 7.4) affects GitLab versions from 18.6 through 18.8.1 and poses a significant risk to account security.
| CVE ID | Vulnerability | CVSS Score | Severity |
|---|---|---|---|
| CVE-2026-0723 | Unchecked Return Value in authentication services (2FA bypass) | 7.4 | High |
| CVE-2025-13927 | Denial of Service in Jira Connect integration | 7.5 | High |
| CVE-2025-13928 | Incorrect Authorization in Releases API | 7.5 | High |
| CVE-2025-13335 | Infinite Loop in Wiki redirects | 6.5 | Medium |
| CVE-2026-1102 | Denial of Service in API endpoint (SSH requests) | 5.3 | Medium |
Security researcher ahacker1 discovered and reported the flaw through GitLab’s HackerOne bug bounty program.
Organizations relying on two-factor authentication for privileged accounts should prioritize this patch immediately.
GitLab also patched three denial-of-service issues that unauthenticated attackers could exploit:
Attackers can cause a denial-of-service condition by sending repeated malformed SSH authentication requests. However, this medium-severity flaw (CVSS 5.3) has a lower impact.
Additionally, CVE-2025-13335 addresses an infinite loop issue in Wiki redirects, allowing authenticated users to create specially crafted Wiki documents that bypass cycle detection and cause service disruptions.
GitLab emphasizes that all self-managed installations running affected versions must upgrade to the latest patch release immediately.
Single-node deployments will experience downtime during migration, whereas multi-node installations can implement zero-downtime upgrade procedures.
Follow us on Google News, LinkedIn, and X to Get Instant Updates ancd Set GBH as a Preferred Source in Google.
Attackers abused compromised ConnectWise Cloud Backup credentials to access Microsoft 365 customer environments, prompting ConnectWise…
Anthropic says an internal Claude research model reconstructed how the National Security Agency generated seeds…
Two WordPress Core vulnerabilities can be chained to execute remote code without authentication, according to…
A newly disclosed OpenBSD kernel exploitation chain combines a shared memory accounting flaw with a…
GhostAction attackers have expanded their GitHub credential theft campaign with a second stage that disguises…
Indian authorities have warned that SideCopy hackers are targeting Indian organizations, including academic institutions, with…