Skip to main content

GitLab CE/EE EUVDEUVD-2025-209549

| CVE-2025-0186 MEDIUM
Allocation of Resources Without Limits or Throttling (CWE-770)
2026-04-22 GitLab GHSA-vhmr-xxmg-qhfg
6.5
CVSS 3.1 · NVD
Share

Severity by source

NVD PRIMARY
6.5 MEDIUM
AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

7
PoC Detected
Apr 23, 2026 - 20:51 vuln.today
Public exploit code
Patch released
Apr 23, 2026 - 20:51 nvd
Patch available
Analysis Generated
Apr 23, 2026 - 00:18 vuln.today
Patch available
Apr 22, 2026 - 17:33 EUVD
EUVD ID Assigned
Apr 22, 2026 - 16:31 euvd
EUVD-2025-209549
Analysis Generated
Apr 22, 2026 - 16:31 vuln.today
CVE Published
Apr 22, 2026 - 16:05 nvd
MEDIUM 6.5

DescriptionCVE.org

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 10.6 before 18.9.6, 18.10 before 18.10.4, and 18.11 before 18.11.1 that could have allowed an authenticated user to cause denial of service under certain conditions by exhausting server resources by making crafted requests to a discussions endpoint.

AnalysisAI

Authenticated users can trigger denial of service in GitLab CE/EE versions 10.6 through 18.11.0 by sending crafted requests to the discussions endpoint that exhaust server resources. The vulnerability requires valid authentication credentials and affects all affected versions across the 10.6, 18.9, 18.10, and 18.11 release branches. Publicly available exploit code exists; CISA has not yet listed this in the Known Exploited Vulnerabilities catalog, but active exploitation likelihood is moderate given public POC availability and the low complexity of resource exhaustion attacks.

Technical ContextAI

The vulnerability resides in GitLab's discussions endpoint (API or web interface handler) and involves improper resource consumption controls, classified under CWE-770 (Allocation of Resources Without Limits or Throttling). The affected product is GitLab Community Edition and Enterprise Edition, a DevOps platform written primarily in Ruby on Rails. The issue stems from insufficient request validation or rate-limiting on the discussions endpoint, allowing authenticated attackers to craft requests that consume excessive CPU, memory, or database resources without triggering protection mechanisms. This is a classic resource exhaustion vector where the endpoint fails to implement per-user or per-request quotas on computationally expensive operations.

RemediationAI

Upgrade immediately to GitLab 18.9.6, 18.10.4, or 18.11.1 depending on the current release branch. For users unable to patch immediately, implement network-level rate-limiting on the discussions endpoint using a reverse proxy (nginx, HAProxy) or GitLab's built-in API rate-limiting features, restricting requests per authenticated user per minute to values appropriate for legitimate discussion activity (e.g., 60-100 requests/minute/user). Monitor CPU and memory utilization on application servers, and consider enabling per-endpoint request timeouts to prevent long-running queries from exhausting resources. Additionally, review GitLab access controls to ensure that external collaborators and service accounts have appropriate permission scopes, reducing the number of authenticated users capable of triggering the endpoint. The patch is confirmed available per vendor advisory (https://about.gitlab.com/releases/2026/04/22/patch-release-gitlab-18-11-1-released/). Side effects of aggressive rate-limiting are rare for discussions workflows, but test in a staging environment to confirm legitimate users are not impacted by the chosen thresholds.

More in Gitlab

View all
CVE-2023-7028 CRITICAL POC
10.0 Jan 12

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.

CVE-2013-4490 MEDIUM POC
6.5 May 13

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

CVE-2021-22205 CRITICAL POC
10.0 Apr 23

An issue has been discovered in GitLab CE/EE affecting all versions starting from 11.9. Rated critical severity (CVSS 10

CVE-2022-2992 CRITICAL POC
9.9 Oct 17

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

CVE-2018-18843 CRITICAL POC
10.0 Dec 04

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

CVE-2024-45409 CRITICAL POC
9.8 Sep 10

The Ruby SAML library is for implementing the client side of a SAML authorization. Rated critical severity (CVSS 9.8), t

CVE-2022-1162 CRITICAL POC
9.8 Apr 04

A hardcoded password was set for accounts registered using an OmniAuth provider (e.g. Rated critical severity (CVSS 9.8)

CVE-2022-0735 CRITICAL POC
9.8 Mar 28

An issue has been discovered in GitLab CE/EE affecting all versions starting from 12.10 before 14.6.5, all versions star

CVE-2021-22175 CRITICAL POC
9.8 Jun 11

When requests to the internal network for webhooks are enabled, a server-side request forgery vulnerability in GitLab af

CVE-2021-22203 CRITICAL POC
9.8 Apr 02

An issue has been discovered in GitLab CE/EE affecting all versions starting from 13.7.9 before 13.8.7, all versions sta

CVE-2019-15741 CRITICAL POC
9.8 Sep 16

An issue was discovered in GitLab Omnibus 7.4 through 12.2.1. Rated critical severity (CVSS 9.8), this vulnerability is

CVE-2019-6960 CRITICAL POC
9.8 Sep 09

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

Share

EUVD-2025-209549 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy