CVE-2024-1816VulnerabilityPublished 28 Jun 2024Updated 10 Sep 2026

CVE-2024-1816: GitLab · Uncontrolled Resource Consumption

Affects gitlabSource GCVE Database

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

Data as of 26 Oct 2026, 06:26 UTC

Severity

Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 17.1.1, 17.0.3, 16.11.5

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Jun 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 2026-10-26.

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 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 17.1.1, 17.0.3 or 16.11.5.

Affected software

Product	Affected	Fixed in
Bitnamigitlab`pkg:bitnami/gitlab`Other threats	Affected >=12.0.0 <16.11.5 >=17.0.0 <17.0.3 >=17.1.0 <17.1.1	Fixed in 16.11.5 17.0.3 17.1.1

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 available for GitLab CE/EE versions prior to 16.11.5, 17.0.3, and 17.1.1. Upgrading to fixed versions will mitigate the vulnerability. No additional mitigation steps are indicated.

Description

A vulnerability in GitLab CE/EE allows an attacker to cause denial of service via crafted OpenAPI files. This affects multiple version ranges from 12.0 up to but not including 16.11.5, 17.0 up to 17.0.3, and 17.1 up to 17.1.1. The issue results in uncontrolled resource consumption leading to service disruption. A patch is available to address this vulnerability.

Impact

Successful exploitation allows an attacker to cause denial of service by exhausting resources through crafted OpenAPI files. This can disrupt GitLab services, impacting availability for users.

Summary

CVE-2024-1816 is an uncontrolled resource consumption vulnerability in GitLab CE/EE. It affects all versions starting from 12.0 prior to 16.11.5, from 17.0 prior to 17.0.3, and from 17.1 prior to 17.1.1. An attacker can exploit this by submitting a crafted OpenAPI file, causing denial of service conditions due to resource exhaustion. The vulnerability has a medium severity rating and no known exploits in the wild have been reported. A patch is available for the affected versions.

References

Community reviews

Loading reviews…