GitLab Patches High-Severity 2FA Bypass and DoS Vulnerabilities in CE/EE
GitLab released security updates for self-managed GitLab Community Edition (CE) and Enterprise Edition (EE) to fix a high-severity two-factor authentication (2FA) bypass and multiple denial-of-service (DoS) flaws. The most significant issue, CVE-2026-0723 (CVSS 7.4), is an unchecked return value weakness in authentication services that could allow an attacker with knowledge of a victim’s credential/account ID to bypass 2FA by submitting forged device responses.
GitLab also patched DoS vulnerabilities affecting unauthenticated and authenticated scenarios, including crafted malformed authentication data against the Jira Connect integration (CVE-2025-13927), incorrect authorization validation in API endpoints such as the Releases API (CVE-2025-13928), malformed Wiki documents that bypass cycle detection (CVE-2025-13335), and repeated malformed SSH authentication requests (CVE-2026-1102). Fixed releases are 18.8.2, 18.7.2, and 18.6.4; GitLab advised administrators to upgrade immediately, noting GitLab.com is already patched, while third-party tracking indicated thousands of exposed GitLab CE instances remain online and potentially at risk if unpatched.
Get ahead of threats like this
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
How this story unfolded
2 events from the most recent confirmed update back to the earliest known activity.
GitLab urges self-managed admins to upgrade immediately
In its advisory, GitLab warned self-managed customers to apply the new releases quickly because unpatched instances could face service disruption or account compromise. GitLab also stated that GitLab.com was already running patched code and that GitLab Dedicated customers did not need to take action.
GitLab releases patches for 2FA bypass and DoS vulnerabilities
GitLab issued security updates 18.8.2, 18.7.2, and 18.6.4 for self-managed Community Edition and Enterprise Edition instances to fix multiple vulnerabilities. The patched issues include CVE-2026-0723, a high-severity two-factor authentication bypass flaw, along with four denial-of-service vulnerabilities affecting Jira Connect, the Releases API, Wiki redirects, and SSH authentication handling.
Related entities
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
Sources
5 references tracked. Mallory keeps watching after this page renders.
GitLab Patch Release Fixes High-Severity Vulnerabilities
thecyberexpress.com
Open sourceGitLab patches critical 2FA bypass vulnerability | SC Media
scworld.com
Open sourceMultiple GitLab Vulnerabilities Enables 2FA Bypass and DoS Attacks
cybersecuritynews.com
Open sourceGitLab warns of high-severity 2FA bypass, denial-of-service flaws
bleepingcomputer.com
Open sourceGitLab Alert: High-Severity 2FA Bypass & DoS Flaws Patched in Urgent Update
securityonline.info
Open sourceSee the full picture, correlated to your attack surface.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Related stories
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
GitLab patches 11 flaws including account takeover and XSS in CE and EE
GitLab released **19.0.2**, **18.11.5**, and **18.10.8** for self-managed Community Edition and Enterprise Edition deployments to fix **11 security vulnerabilities** and additional bugs, and urged administrators to upgrade immediately. The advisory says all versions before those releases are affected, while **GitLab.com** has already been patched and **GitLab Dedicated** customers do not need to take action. GitLab also warned that the update includes database migrations that may cause downtime on single-node instances, though multi-node environments can use zero-downtime upgrade procedures. The most severe issue, **`CVE-2026-6552`** (**CVSS 8.7**), is an improper authorization flaw in GitLab EE's Group SAML identity management that could let an authenticated **group Owner** take over another group member's account under certain conditions. GitLab also fixed **`CVE-2026-10087`**, an Analytics Dashboard cross-site scripting flaw in GitLab EE that could allow an authenticated **developer** to execute arbitrary client-side code in a victim's browser. The broader patch set addresses additional risks including denial of service in Grape API JSON parsing, SSRF, unauthorized access to confidential data, and other authorization bypasses, and government and vendor advisories have called on organizations to apply the patched versions.
Jun 11, 2026
GitLab Patches XSS and API Denial-of-Service Vulnerabilities in CE/EE
GitLab released security updates for **GitLab Community Edition (CE)** and **Enterprise Edition (EE)**, shipping patched versions **18.9.2**, **18.8.6**, and **18.7.6** to address multiple vulnerabilities affecting self-managed deployments. The Canadian Centre for Cyber Security issued advisory **AV26-222** urging organizations to review GitLab’s upstream advisory and apply the updates for any instances running versions prior to those releases. The update fixes **15 security issues**, including a high-severity **XSS** vulnerability (**CVE-2026-1090**, CVSS 8.7) in Markdown placeholder processing when the relevant feature flag is enabled, which could allow an authenticated attacker to inject malicious JavaScript into a victim’s browser. GitLab also addressed several **denial-of-service** conditions, including issues impacting the **GraphQL API** (resource exhaustion via recursion), repository archive endpoints, and JSON payload validation in the protected branches API; additional fixes include webhook-related DoS risks (e.g., **CVE-2025-13690**, **CVE-2025-12576**) and a **CRLF sequence** handling issue (**CVE-2026-3848**).
Mar 27, 2026
GitLab Patches XSS and Unauthenticated DoS Flaws in Self-Managed CE and EE
GitLab issued emergency security updates for self-managed Community Edition and Enterprise Edition instances to fix multiple high-severity vulnerabilities, including several cross-site scripting (**XSS**) flaws and unauthenticated denial-of-service (**DoS**) issues. The XSS bugs could allow attackers to run malicious JavaScript in users’ browsers, potentially leading to session hijacking, token theft, and repository manipulation, while the DoS flaws could disrupt CI/CD pipelines and broader workflow operations. The affected products are GitLab CE and EE versions earlier than `18.11.3`, `18.10.6`, and `18.9.7`, and administrators were urged to review GitLab’s release guidance and upgrade immediately to those patched versions. GitLab said its cloud-hosted platforms had already been remediated, while self-hosted operators were warned that single-node upgrades require downtime because of database migrations, whereas multi-node deployments can follow standard zero-downtime upgrade procedures.
May 14, 2026