Cyber Resilience

CVE-2025-14511

Gitlab 12.2.0 – 18.7.5

Published
25 February 2026
Modified
28 February 2026
Patch / advisory
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0035 28th percentile
Risk Priority 57 floored blend · peak EPSS

Summary

CVE-2025-14511 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 28th 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-14511 is a denial-of-service vulnerability (CWE-1284) affecting GitLab Community Edition (CE) and Enterprise Edition (EE) in all versions from 12.2 prior to 18.7.5, 18.8 prior to 18.8.5, and 18.9 prior to 18.9.1. The flaw exists in the container registry event endpoint, where an unauthenticated user could send specially crafted files under certain conditions to trigger resource exhaustion. It carries 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).

An unauthenticated attacker with network access to a vulnerable GitLab instance can exploit this by submitting malicious files to the container registry event endpoint. Exploitation requires low complexity and no user interaction or privileges, resulting in denial of service through high availability impact, such as disrupting registry operations without compromising confidentiality or integrity.

GitLab has remediated the issue via patches in versions 18.7.5, 18.8.5, and 18.9.1, as detailed in the February 25, 2026 patch release notes for 18.9.1. Administrators should upgrade affected instances immediately. Further technical details are documented in GitLab issue #583717 and the corresponding HackerOne report #3452200.

EU & UK References

Vulnerability Data

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 12.2 before 18.7.5, 18.8 before 18.8.5, and 18.9 before 18.9.1 that could have allowed an unauthenticated user to cause denial of service by sending specially crafted files to…

more

the container registry event endpoint under certain conditions.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
T1499 Endpoint Denial of Service Impact
Adversaries may perform Endpoint Denial of Service (DoS) attacks to degrade or block the availability of services to users.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-1101Same product: Gitlab Gitlab
CVE-2025-13078Same product: Gitlab Gitlab
CVE-2025-14869Same product: Gitlab Gitlab
CVE-2025-2256Same product: Gitlab Gitlab
CVE-2025-14513Same product: Gitlab Gitlab
CVE-2025-10094Same product: Gitlab Gitlab
CVE-2026-1092Same product: Gitlab Gitlab
CVE-2025-12664Same product: Gitlab Gitlab
CVE-2023-3900Same product: Gitlab Gitlab
CVE-2026-2370Same product: Gitlab Gitlab

Affected Assets

gitlab
gitlab
18.9.0 · 12.2.0 — 18.7.5 · 12.2.0 — 18.7.5 · 18.8.0 — 18.8.5

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V6.7.2
  • V1.4.2
  • V2.1.1
  • V2.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.

PR.PS-06 mostly match
prevents

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.

finds

Security testing in development can detect missing quantity validation but does not itself implement the control.

prevents

Secure development lifecycle mandates input validation for quantity fields, directly preventing CWE-1284.

prevents

Application security requirements explicitly call for validation of size/length inputs, mitigating CWE-1284.

prevents

Secure architecture principles encourage robust input handling but do not specifically address quantity validation.

prevents

Secure coding standards require explicit checks on numeric quantity inputs, fully addressing CWE-1284.

References