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
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
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. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Attacker must hold an active, authenticated GitLab session (PR:L per CVSS vector) - no elevated or administrative privileges are required. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H) scores 6.5 Medium, reflecting a network-accessible, low-complexity attack requiring only an authenticated session. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker registers or logs into a GitLab instance and uploads a specially crafted file - such as a malformed archive or a format with pathological nesting - to a GitLab project via the web UI or API. The GitLab server begins processing the file, consuming unbound CPU or memory resources, causing the instance to become unresponsive or crash for all concurrent users. … |
| Remediation | 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. … Detailed patch versions, workarounds, and compensating controls in full report. |
Threat intelligence, references, and detailed analysis are available after sign-in.
More from same product – last 7 days
Stored cross-site scripting and account integrity abuse in GitLab Enterprise Edition versions 13.1.4 through 18.10.7, 18
Stored cross-site scripting in GitLab Enterprise Edition's Analytics Dashboard allows an authenticated developer-role us
Account takeover in GitLab Enterprise Edition versions 15.5 through 19.0.2 allows an authenticated group Owner to hijack
Denial of service in GitLab CE/EE versions 12.10 through 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2 allows un
Incorrect authorization enforcement in GitLab CE/EE exposes hidden merge requests to unauthorized modification by authen
Share
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-36233
GHSA-jfx9-cc6f-6x6q