What is the CVSS score of CVE-2025-6016?

CVE-2025-6016 has a CVSS 3.1 base score of 6.5 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H. EPSS exploitation probability: 0.0%.

Is there a public PoC exploit available for CVE-2025-6016?

Yes, a public proof-of-concept exploit is available for CVE-2025-6016. Prioritise patching immediately. EPSS: 0.0%.

Is there a patch available for CVE-2025-6016?

Yes, a patch is available for CVE-2025-6016. Update the affected software to the latest version immediately.

GitLab CE/EE CVE-2025-6016

EUVD-2025-209555 MEDIUM

Allocation of Resources Without Limits or Throttling (CWE-770)

2026-04-22 GitLab

GHSA-4cg5-m8c9-x738

Gitlab Denial Of Service

6.5

CVSS 3.1 · NVD

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

PoC Detected

Apr 23, 2026 - 20:49 vuln.today

Public exploit code

Patch released

Apr 23, 2026 - 20:49 nvd

Patch available

Analysis Generated

Apr 23, 2026 - 00:17 vuln.today

Patch available

Apr 22, 2026 - 17:33 EUVD

EUVD ID Assigned

Apr 22, 2026 - 16:31 euvd

EUVD-2025-209555

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 9.2 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 due to insufficient resource allocation limits when retrieving notes under certain conditions.

AnalysisAI

Denial of service in GitLab CE/EE affects authenticated users who can trigger resource exhaustion when retrieving notes under specific conditions, causing service unavailability. Versions 9.2 through 18.9.5, 18.10.0 through 18.10.3, and 18.11.0 are vulnerable. An authenticated attacker with standard user privileges can exploit this remotely without user interaction via crafted note retrieval requests. A publicly available exploit exists, and patches have been released by GitLab.

Technical ContextAI

The vulnerability stems from insufficient resource allocation limits (CWE-770) in GitLab's note retrieval functionality. When processing certain note requests, the application fails to properly constrain memory or CPU consumption, allowing an authenticated user to trigger unbounded resource allocation. This is a classic resource exhaustion attack vector affecting web application backends. The vulnerability requires authentication (PR:L in CVSS vector) but operates over the network with low attack complexity, suggesting the vulnerable code path is easily reachable and does not require special preconditions beyond basic user access.

RemediationAI

Upgrade immediately to GitLab 18.9.6, 18.10.4, or 18.11.1 or later, depending on your current version branch. For organizations unable to patch immediately, implement network-level rate limiting on authenticated API endpoints related to note retrieval (identify via GitLab API documentation), and restrict note retrieval endpoints to trusted internal networks only if the feature is not essential for external users. Monitor GitLab application logs and resource metrics for unusual CPU or memory spikes correlated with note retrieval API calls, which may indicate exploitation attempts. Note that these controls may impact legitimate note access patterns and should be tested in a staging environment before production deployment. See GitLab advisory at https://about.gitlab.com/releases/2026/04/22/patch-release-gitlab-18-11-1-released/ and the detailed issue at https://gitlab.com/gitlab-org/gitlab/-/work_items/548940 for additional context.