VulnerabilityPublished 24 May 2024Updated 10 Sep 2026

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

Affects gitlabSource GCVE Database

Not known to be exploited · fixed in 16.11.2 : update gitlab when convenient.

Data as of 26 Oct 2026, 10:12 UTC

Severity

Medium

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 0.7% chance of exploitation in 30 days – higher than 55% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 16.11.2, 16.10.5, 16.9.7

Exploitation evidence

Disclosed: evidence found.
CVE published 24 May 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade gitlab to 16.11.2, 16.10.5 or 16.9.7.

Affected software

Product	Affected	Fixed in
Bitnamigitlab`pkg:bitnami/gitlab`Other threats	Affected >=15.4.0 <16.9.7 >=16.10.0 <16.10.5 >=16.11.0 <16.11.2	Fixed in 16.9.7 16.10.5 16.11.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available for this vulnerability. Users should upgrade to versions 16.9.7 or later, 16.10.5 or later, or 16.11.2 or later to remediate the issue.

Description

A vulnerability in GitLab CE/EE allows abuse of the API filtering branches and tags to cause a denial of service by allocating resources without limits or throttling. This affects multiple version ranges prior to patched releases. The issue can be exploited to disrupt service availability.

Impact

Successful exploitation can lead to denial of service by exhausting resources through unthrottled API requests filtering branches and tags. This impacts the availability of GitLab services on affected versions.

Summary

CVE-2024-4539 is a denial of service vulnerability in GitLab Community and Enterprise Editions. It arises from the lack of limits or throttling when using the API to filter branches and tags. This flaw affects versions from 15.4 up to but not including 16.9.7, from 16.10 up to but not including 16.10.5, and from 16.11 up to but not including 16.11.2. Exploiting this issue can cause excessive resource consumption leading to service disruption.

References

Community reviews

Loading reviews…