EUVD-2026-20791
GHSA-ffch-rw3v-4mvx
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Primary rating from Vendor (gitlab) · only source for this CVE.
CVSS VectorVendor: gitlab
Lifecycle Timeline
4DescriptionCVE.org
GitLab has remediated an issue in GitLab EE affecting all versions from 18.2 before 18.8.9, 18.9 before 18.9.5, and 18.10 before 18.10.3 that could have allowed an authenticated user to cause denial of service to the GitLab instance due to improper input validation in GraphQL queries.
AnalysisAI
Denial of service in GitLab EE 18.2-18.10 allows authenticated users to crash the GitLab instance through improper input validation in GraphQL queries. GitLab EE versions 18.2 before 18.8.9, 18.9 before 18.9.5, and 18.10 before 18.10.3 are affected. An authenticated attacker with any valid GitLab account can trigger the vulnerability by submitting a malformed GraphQL query, causing the instance to become unavailable. No public exploit code has been identified at the time of analysis, and the vulnerability is not listed in CISA's Known Exploited Vulnerabilities catalog.
Technical ContextAI
The vulnerability stems from improper input validation in GitLab's GraphQL query handler (CWE-1284: Improper Validation of Specified Quantity in Input). GraphQL, a query language for APIs, can process complex nested queries and mutations. The flaw allows an authenticated GraphQL client to submit requests that bypass validation checks, causing excessive resource consumption (CPU, memory, or query processing overhead) that leads to denial of service. This is a classic case of insufficient input sanitization before GraphQL query execution, affecting GitLab EE's application layer rather than database or infrastructure components.
RemediationAI
Vendor-released patch: GitLab EE 18.8.9, 18.9.5, or 18.10.3 depending on your current major version. Administrators must upgrade immediately to the nearest patched version for your release series. For instances on 18.2-18.8.x, upgrade to 18.8.9 or later; for 18.9.x, upgrade to 18.9.5 or later; for 18.10.x, upgrade to 18.10.3 or later. As a temporary workaround pending upgrade, restrict GraphQL query access by disabling the GraphQL API endpoint or implementing rate-limiting and query depth/complexity restrictions at the reverse proxy or WAF level. Refer to the official patch release notes at https://about.gitlab.com/releases/2026/04/08/patch-release-gitlab-18-10-3-released/ for complete upgrade instructions and validation steps.
An issue has been discovered in GitLab CE/EE affecting all versions starting from 11.9. Rated critical severity (CVSS 10
An issue has been discovered in GitLab CE/EE affecting all versions from 16.1 prior to 16.1.6, 16.2 prior to 16.2.9, 16.
Unauthenticated arbitrary file read in GitLab CE/EE lets remote attackers retrieve files from the GitLab server via the
The SSH key upload feature (lib/gitlab_keys.rb) in gitlab-shell before 1.7.3, as used in GitLab 5.0 before 5.4.1 and 6.x
A vulnerability in GitLab CE/EE affecting all versions from 11.10 prior to 15.1.6, 15.2 to 15.2.4, 15.3 to 15.3.2 allows
Sensitive credential and configuration disclosure in GitLab Enterprise Edition allows an authenticated user with Duo Cha
The Kubernetes integration in GitLab Enterprise Edition 11.x before 11.2.8, 11.3.x before 11.3.9, and 11.4.x before 11.4
The Ruby SAML library is for implementing the client side of a SAML authorization. Rated critical severity (CVSS 9.8), t
A hardcoded password was set for accounts registered using an OmniAuth provider (e.g. Rated critical severity (CVSS 9.8)
An issue has been discovered in GitLab CE/EE affecting all versions starting from 12.10 before 14.6.5, all versions star
When requests to the internal network for webhooks are enabled, a server-side request forgery vulnerability in GitLab af
An issue has been discovered in GitLab CE/EE affecting all versions starting from 13.7.9 before 13.8.7, all versions sta
Same technique Denial Of Service
View allShare
External POC / Exploit Code
Leaving vuln.today