GitLab has released a critical security advisory alongside versions 18.10.1, 18.9.3, and 18.8.7 for its Community (CE) and Enterprise Editions (EE). The release addresses a battery of vulnerabilities, including several High-severity flaws that could allow attackers to impersonate applications, execute unauthorized commands, or paralyze instances through Denial of Service (DoS) attacks.
The most pressing fixes involve improper authorization and missing request protections that could lead to a total loss of account integrity.
- Jira Connect Impersonation (CVE-2026-2370): GitLab remediated an issue where an authenticated user with minimal permissions could “obtain installation credentials and impersonate the GitLab app”. This high-severity flaw (CVSS 8.1) impacted all versions from 14.3 up to the latest patched releases.
- GLQL API Mutation (CVE-2026-3857): Another CVSS 8.1 flaw could have allowed unauthenticated attackers to “execute arbitrary GraphQL mutations on behalf of authenticated users” due to a lack of Cross-Site Request Forgery (CSRF) protections.
The update also targets vulnerabilities that could allow attackers to manipulate user data or leak sensitive backend secrets.
- HTML Injection in Reports (CVE-2026-2995): In the Enterprise Edition, improper sanitization of HTML content in vulnerability reports could have allowed users to “add email addresses to targeted user accounts”.
- AI Model Token Leak (CVE-2026-1724): A medium-severity flaw in GraphQL queries was found to expose “API tokens of self-hosted AI models” to unauthenticated users.
Several vulnerabilities focused on resource exhaustion, allowing attackers to make GitLab instances “unresponsive”. These DoS issues were found in:
- GraphQL Request Processing: Triggered by unauthenticated users through improper input validation.
- CI Configuration & Webhooks: Authenticated users could cause DoS due to “excessive resource consumption” when processing specific CI or webhook inputs.
Administrators should check their current version immediately. If you are running any version between 14.3 and 18.10, you are likely affected. To protect your workspace, “upgrade to the latest version as soon as possible”.
Support Our Threat Intelligence
If you find our CVE report and cybersecurity news helpful, consider supporting our work.