Cyber Resilience

CVE-2025-2256

Gitlab 7.12.0 – 18.1.6

Published
12 September 2025
Modified
20 September 2025
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.0047 38th percentile
Risk Priority 55 floored blend · peak EPSS

Summary

CVE-2025-2256 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, ranked at the 38th 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 AC-10 (Concurrent Session Control) and SC-5 (Denial-of-service Protection) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

An issue has been discovered in GitLab CE/EE affecting all versions from 7.12 before 18.1.6, 18.2 before 18.2.6, and 18.3 before 18.3.2 that could have allowed unauthorized users to render the GitLab instance unresponsive to legitimate users by sending multiple…

more

concurrent large SAML responses.

CWE(s)

Related Threats

CVEs Like This One

CVE-2025-10094Same product: Gitlab Gitlab
CVE-2026-1092Same product: Gitlab Gitlab
CVE-2025-14869Same product: Gitlab Gitlab
CVE-2025-13078Same product: Gitlab Gitlab
CVE-2025-12664Same product: Gitlab Gitlab
CVE-2025-14513Same product: Gitlab Gitlab
CVE-2025-14511Same product: Gitlab Gitlab
CVE-2026-1101Same product: Gitlab Gitlab
CVE-2023-2030Same product: Gitlab Gitlab
CVE-2026-13151Same product: Gitlab Gitlab

Affected Assets

gitlab
gitlab
7.12.0 — 18.1.6 · 7.12.0 — 18.1.6 · 18.2.0 — 18.2.6

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SC-5 Denial-of-service Protection
  • AC-10 Concurrent Session Control
  • SI-10 Information Input Validation
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

prevent

Directly requires mechanisms to protect against or limit the effects of denial-of-service attacks, including resource exhaustion from concurrent large SAML responses.

prevent

Limits the number of concurrent sessions or authentication requests an unauthenticated user can initiate, directly blocking the multiple concurrent SAML responses described in the CVE.

prevent

Enforces validation of input size and structure on SAML responses before processing, mitigating the oversized payloads that trigger resource exhaustion.

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.

detects

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