GitLab and Gitea Flaws Prompt Advisories Over Multiple Security Risks
German authorities issued multiple security advisories for GitLab and Gitea, warning of newly tracked vulnerabilities that affect widely used source code management and DevOps platforms. Two separate dCERT notices flagged multiple vulnerabilities in GitLab, indicating more than one security issue requiring administrator attention across the platform.
A separate dCERT advisory warned that Gitea contains a vulnerability that can bypass security measures, raising concern that protections intended to restrict access or enforce policy may be circumvented. While the advisories did not publish technical synopses in the referenced notices, the alerts indicate that organizations using GitLab or Gitea should review vendor guidance, identify affected deployments, and prioritize patching or other mitigations.
Timeline
Apr 23, 2026
dCERT publishes GitLab multiple vulnerabilities advisory 2026-1221
dCERT issued advisory 2026-1221 concerning multiple vulnerabilities in GitLab. The reference content does not specify whether this is a new set of flaws or an update to earlier reporting.
Apr 23, 2026
dCERT publishes Gitea security bypass advisory 2026-1216
dCERT issued advisory 2026-1216 for a Gitea vulnerability that allows bypassing security measures. The reference does not include additional technical or impact details.
Mar 25, 2026
dCERT publishes GitLab multiple vulnerabilities advisory 2026-0833
dCERT issued advisory 2026-0833 concerning multiple vulnerabilities affecting GitLab. No further technical details are provided in the reference content.
See the full picture in Mallory
Mallory subscribers get deeper analysis on every story, including:
Who’s affected and how
Deep-dive technical analysis
Actionable next steps for your team
IPs, domains, hashes, and more
Ask questions and take action on every story
Filter by topic, classification, timeframe
Get matching stories delivered automatically
Sources
Related Stories
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.
1 months ago
Critical Unauthenticated Remote Code Execution Flaws Disclosed in GitLab and Apache Commons Text
Authorities warned of **critical vulnerabilities** in **GitLab Community Edition and Enterprise Edition** and the **Apache Commons Text** component that could be exploited remotely over a network. In both cases, the flaws were described as reachable **without physical access**, requiring **no user interaction** and **no prior authentication**, making internet-exposed systems particularly at risk. The advisories indicate that attackers could target the vulnerable software directly rather than relying on phishing or stolen credentials, raising the likelihood of rapid opportunistic exploitation. Organizations using affected GitLab deployments or applications that include Apache Commons Text were urged to identify exposed assets quickly and prioritize remediation because the weaknesses could enable severe compromise through unauthenticated remote attacks.
2 weeks ago
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**).
1 months ago