CVE-2025-14513
Gitlab 16.11.0 – 18.7.6
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HSummary
CVE-2025-14513 is a high-severity Improper Validation of Specified Quantity in Input (CWE-1284) vulnerability in Gitlab Gitlab. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 39th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-14513 is a vulnerability in GitLab Community Edition (CE) and Enterprise Edition (EE) that enables an unauthenticated user to trigger a denial of service (DoS) condition. The flaw arises from improper input validation when processing specially crafted JSON payloads submitted to the protected branches API. It impacts all versions from 16.11 prior to 18.7.6, 18.8 prior to 18.8.6, and 18.9 prior to 18.9.2, with a CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) and is associated with CWE-1284 (Improper Validation of Specified Quantity in Input).
An unauthenticated attacker can exploit this remotely over the network with low attack complexity and no user interaction or privileges needed. By sending a malicious JSON payload to the protected branches API endpoint, the attacker causes a DoS, rendering the service unavailable, while confidentiality and integrity remain unaffected.
GitLab has remediated the issue through patches, including GitLab 18.9.2 as outlined in the patch release notes at https://about.gitlab.com/releases/2026/03/11/patch-release-gitlab-18-9-2-released/. Further technical details are documented in GitLab's internal work item at https://gitlab.com/gitlab-org/gitlab/-/work_items/583718 and the originating HackerOne disclosure report at https://hackerone.com/reports/3452477. Security teams should prioritize upgrading affected instances to patched versions for mitigation.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-208576
Vulnerability Data
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 16.11 before 18.7.6, 18.8 before 18.8.6, and 18.9 before 18.9.2 that could have allowed an unauthenticated user to cause a denial of service condition due to improper input…
more
validation when processing specially crafted JSON payloads in the protected branches API.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V6.7.2V1.4.2V2.1.1V2.2.1
Mitigating Controls (NIST 800-53 r5) AI
SI-10 requires validity checks on information inputs, directly stopping acceptance of malformed quantities before they can be used.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require proper quantity/length validation in input handling.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development can detect missing quantity validation but does not itself implement the control.
Secure development lifecycle mandates input validation for quantity fields, directly preventing CWE-1284.
Application security requirements explicitly call for validation of size/length inputs, mitigating CWE-1284.
Secure architecture principles encourage robust input handling but do not specifically address quantity validation.
Secure coding standards require explicit checks on numeric quantity inputs, fully addressing CWE-1284.