CVE-2024-2818: Allocation of Resources Without Limits or Throttling in GitLab
Affects gitlabSource GCVE Database
Not known to be exploited · fixed in 16.10.1 : update gitlab when convenient.
Data as of 26 Oct 2026, 10:12 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
- EPSS
- 0.9% chance of exploitation in 30 days – higher than 60% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 16.10.1, 16.9.3, 16.8.5
Exploitation evidence
Disclosed: evidence found.
CVE published 3 Apr 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.
What to do
Upgrade gitlab to 16.10.1, 16.9.3 or 16.8.5.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Bitnamigitlabpkg:bitnami/gitlabOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Apply the official patches by upgrading GitLab to versions 16.8.5, 16.9.3, or 16.10.1 or later. Since patches are available, updating to these fixed versions fully mitigates the vulnerability.
Description
A resource allocation vulnerability in GitLab CE/EE allows attackers to cause a denial of service by submitting maliciously crafted label description parameters. This affects multiple version ranges before patched releases. The issue has been fixed in versions 16.8.5, 16.9.3, and 16.10.1.