CVE-2024-2434VulnerabilityPublished 27 Apr 2024Updated 10 Sep 2026

CVE-2024-2434: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in GitLab

Affects gitlabSource GCVE Database

Not known to be exploited · 23% EPSS · fixed in 16.11.1 : patch gitlab soon.

Data as of 25 Oct 2026, 19:02 UTC

Severity

High

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

EPSS: 23.1% chance of exploitation in 30 days – higher than 97% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 16.11.1, 16.10.4, 16.9.6

Exploitation evidence

Disclosed: evidence found.
CVE published 27 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 2026-10-25.

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 16.11.1, 16.10.4 or 16.9.6.

Affected software

Product	Affected	Fixed in
Bitnamigitlab`pkg:bitnami/gitlab`Other threats	Affected >=16.9.0 <16.9.6 >=16.10.0 <16.10.4 >=16.11.0 <16.11.1	Fixed in 16.9.6 16.10.4 16.11.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 by upgrading GitLab to versions 16.9.6, 16.10.4, or 16.11.1 or later. Since a patch is available, remediation should be performed promptly to mitigate the risk.

Description

GitLab versions 16.9 prior to 16.9.6, 16.10 prior to 16.10.4, and 16.11 prior to 16.11.1 contain a path traversal vulnerability. This flaw allows an attacker to bypass pathname restrictions, potentially leading to denial of service (DoS) and unauthorized reading of restricted files. The issue affects both GitLab CE and EE editions. A patch is available to address this vulnerability.

Impact

Exploitation of this vulnerability can lead to denial of service conditions and unauthorized access to restricted files within the GitLab environment. This could impact the confidentiality and availability of the affected system. No active exploitation has been reported.

Summary

CVE-2024-2434 is a path traversal vulnerability in GitLab CE/EE affecting versions 16.9.0 up to but not including 16.9.6, 16.10.0 up to but not including 16.10.4, and 16.11.0 up to but not including 16.11.1. The vulnerability allows improper limitation of pathnames to restricted directories, which can be exploited to cause denial of service or read files that should be restricted. No CVSS score is provided. There are no known exploits in the wild. The vulnerability is patched in versions 16.9.6, 16.10.4, and 16.11.1.

References

Community reviews

Loading reviews…