Cyber Posture

CVE-2026-1725

Medium

Published: 25 February 2026

Published
25 February 2026
Modified
28 February 2026
KEV Added
Patch
CVSS Score 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
EPSS Score 0.0005 15.4th percentile
Risk Priority 11 60% EPSS · 20% KEV · 20% CVSS

Summary

CVE-2026-1725 is a medium-severity Allocation of Resources Without Limits or Throttling (CWE-770) vulnerability in Gitlab Gitlab. Its CVSS base score is 5.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Application or System Exploitation (T1499.004); ranked at the 15.4th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

Threat & Defense at a Glance

What attackers do: exploitation maps to Application or System Exploitation (T1499.004).
Threat & Defense Details

Likely Mitigating ControlsAI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-770

This control implements explicit throttling on session allocation, addressing the weakness of allocating resources without limits.

addresses: CWE-770

Plan testing exercises resource allocation limits and throttling during simulated failures, directly addressing weaknesses that allow unbounded resource use.

addresses: CWE-770

Contingency plan updates ensure recovery strategies address unbounded resource allocation, making it harder for attackers to exploit lack of throttling to cause prolonged outages.

addresses: CWE-770

Provides continuity when unbounded resource allocation at the primary site leads to exhaustion and downtime.

addresses: CWE-770

Alternate services allow operations to continue when primary allocation of resources lacks limits or throttling.

addresses: CWE-770

Explicit planning of security-related actions requires defining limits, windows, and resource allocations, making allocation without throttling far less likely.

addresses: CWE-770

Measures of performance include tracking allocation behavior and throttling effectiveness, reducing the window for resource exhaustion attacks.

addresses: CWE-770

Imposes an inactivity-based limit on network resource allocation, throttling the number of concurrently held connections.

MITRE ATT&CK Enterprise TechniquesAI

T1499.004 Application or System Exploitation Impact
Adversaries may exploit software vulnerabilities that can cause an application or system to crash and deny availability to users.
Why these techniques?

Direct application-layer DoS via crafted API requests causing resource exhaustion (CWE-770), matching T1499.004 Application or System Exploitation.

Confidence: HIGH · MITRE ATT&CK Enterprise v18.1

NVD Description

GitLab has remediated an issue in GitLab CE/EE affecting versions from 18.9 before 18.9.1 that could have under certain conditions, allowed an unauthenticated user to cause denial of service by sending specially crafted requests to a CI jobs API endpoint.

Deeper analysisAI

CVE-2026-1725 is a denial-of-service vulnerability in GitLab Community Edition (CE) and Enterprise Edition (EE), affecting versions from 18.9 prior to 18.9.1. The issue stems from improper resource allocation, mapped to CWE-770 (Allocation of Resources Without Limits or Throttling), and allows an unauthenticated user to trigger a DoS under certain conditions by sending specially crafted requests to a CI jobs API endpoint. It has a CVSS v3.1 base score of 5.3 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L), indicating medium severity with low availability impact but no confidentiality or integrity effects.

An unauthenticated attacker with network access can exploit this vulnerability with low complexity and no user interaction required. By crafting and sending malicious requests to the affected CI jobs API endpoint, the attacker can cause resource exhaustion, leading to degraded performance or temporary unavailability of the GitLab instance for legitimate users.

GitLab remediated the vulnerability in version 18.9.1, as detailed in their patch release advisory. Additional details are available in the GitLab issue tracker (gitlab.com/gitlab-org/gitlab/-/issues/588338) and the originating HackerOne disclosure report (hackerone.com/reports/3519773). Security practitioners should upgrade to 18.9.1 or later to mitigate the issue.

Details

CWE(s)

Affected Products

gitlab
gitlab
18.9.0

CVEs Like This One

CVE-2025-13927Same product: Gitlab Gitlab
CVE-2025-1257Same product: Gitlab Gitlab
CVE-2026-1456Same product: Gitlab Gitlab
CVE-2026-1102Same product: Gitlab Gitlab
CVE-2025-13929Same product: Gitlab Gitlab
CVE-2025-8099Same product: Gitlab Gitlab
CVE-2025-12664Same product: Gitlab Gitlab
CVE-2026-3988Same product: Gitlab Gitlab
CVE-2026-1458Same product: Gitlab Gitlab
CVE-2026-1662Same product: Gitlab Gitlab

References