EUVD-2026-36233
GHSA-jfx9-cc6f-6x6q
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Network-accessible upload endpoint, low complexity, authenticated user required (PR:L); purely an availability impact with no confidentiality or integrity effects.
Primary rating from Vendor (GitLab).
CVSS VectorVendor: GitLab
Lifecycle Timeline
3DescriptionCVE.org
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.10 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2 that under certain conditions could have allowed an authenticated user to cause denial of service due to uncontrolled resource consumption when processing a specially crafted file upload.
AnalysisAI
Uncontrolled resource consumption in GitLab CE/EE's file upload processing pipeline enables any authenticated user to trigger denial of service by submitting a specially crafted file. All self-managed GitLab instances running versions from 17.10 up through the patched releases (18.10.8, 18.11.5, 19.0.2) are affected across both Community and Enterprise Editions. A publicly available exploit exists on HackerOne (report #3517331), though no active exploitation has been confirmed by CISA KEV.
Technical ContextAI
CWE-770 (Uncontrolled Resource Consumption) describes a failure to enforce appropriate limits on the amount of resources a process may consume, here triggered during GitLab's server-side file upload processing. When the application parses or processes attacker-controlled uploaded content, it fails to bound CPU, memory, or I/O usage, allowing a single crafted upload to exhaust server resources. This class of bug commonly appears in format parsers (e.g., archive extraction, image decoders, XML/SVG processors) where deeply nested or malformed structures force exponential or unbounded processing loops. The CPE cpe:2.3:a:gitlab:gitlab:*:*:*:*:*:*:*:* covers all GitLab editions and platforms; the specific internal component handling the triggering upload format is not disclosed in publicly available data.
RemediationAI
Upgrade to the patched releases as directed by the GitLab vendor advisory at https://about.gitlab.com/releases/2026/06/10/patch-release-gitlab-19-0-2-released/: target 18.10.8 if on the 18.10 track, 18.11.5 if on the 18.11 track, or 19.0.2 if on the 19.0 track. If immediate patching is not feasible, consider applying upload size limits at the reverse proxy layer (e.g., nginx client_max_body_size directive) to reduce the volume of data that can be fed to the vulnerable parser - note this may break legitimate large file upload workflows and does not eliminate the vulnerability, only raises the resource cost of triggering it. Rate-limiting authenticated API and web endpoints that accept file uploads (e.g., via nginx limit_req or a WAF rule) can reduce the frequency with which an attacker can trigger the condition. Restricting project creation and file upload permissions to a minimal trusted user set is an additional organizational control for environments that cannot patch immediately.
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.
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
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
An issue was discovered in GitLab Omnibus 7.4 through 12.2.1. Rated critical severity (CVSS 9.8), this vulnerability is
An issue was discovered in GitLab Community and Enterprise Edition 9.x, 10.x, and 11.x before 11.5.8, 11.6.x before 11.6
Same technique File Upload
View allShare
External POC / Exploit Code
Leaving vuln.today