NVD / CVE Program· CNA GitLab

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

Noroxi assessment

Priority: Monitor (action score 39/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 23.1% (FIRST EPSS); higher than 97.7% of all records.
Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: GitLab GitLab 16.10.4, 16.11.1, 16.9.6.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to GitLab GitLab 16.10.4, 16.11.1, 16.9.6 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

An issue has been discovered in GitLab affecting all versions of GitLab CE/EE 16.9 prior to 16.9.6, 16.10 prior to 16.10.4, and 16.11 prior to 16.11.1 where path traversal could lead to DoS and restricted file read.

HighCVSS 8.1 · v3.1—No exploit Fix available

Path traversal

BDU:2024-03307

Published: Apr 25, 2024
Updated: Jun 17, 2026
EPSS: 23.1% · 97th percentile
CWE: CWE-22

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 32 / 40 · 8.1 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 7 / 30 · 23.1%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 8.1
CNA · GitLab: 8.5; 0.4 point gap

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
gitlab	gitlab	cpe:2.3:a:gitlab:gitlab

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

gitlab gitlab16.9.0 and later · before 16.9.6
gitlab gitlab16.10.0 and later · before 16.10.4
gitlab gitlab16.11.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitLab). Independent of NVD's CPE analysis and usually ahead of it.

GitLab GitLab
- 16.9 and later · before 16.9.6affected · semver
- 16.10 and later · before 16.10.4affected · semver
- 16.11 and later · before 16.11.1affected · semver

Same product

gitlab: all records

Other highest-scoring records for the same primary product.

CVE-2021-22205An issue has been discovered in GitLab CE/EE affecting all versions starting from 11.9.KEV
100Now
CVE-2026-85706Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in GitLabKEV
99Now
CVE-2023-7028Weak Password Recovery Mechanism for Forgotten Password in GitLabKEV
97Now

Published before and after this one in the same product

← EarlierCVE-2024-3092Apr 11, 2024 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in GitLab
21Monitor
← EarlierCVE-2024-1347Apr 25, 2024 · Authentication Bypass by Spoofing in GitLab
21Monitor
Later →CVE-2024-2829Apr 25, 2024 · Inefficient Regular Expression Complexity in GitLab
38Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
GitLab GitLab	16.10.4	Vendor (CNA)
GitLab GitLab	16.11.1	Vendor (CNA)
GitLab GitLab	16.9.6	Vendor (CNA)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

[pwnie](https://hackerone.com/pwnie)finder

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2023-2825335 days apartAn issue has been discovered in GitLab CE/EE affecting only version 16.0.0.
60This week
CVE-2024-040291 days apartImproper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in GitLab
40Plan
CVE-2023-3385268 days apartImproper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in GitLab
26Monitor
CVE-2024-8647231 days apartImproper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in GitLab
21Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

CVE-2024-40240 days apartAuthentication Bypass by Assumed-Immutable Data in GitLab
39Monitor
CVE-2024-13470 days apartAuthentication Bypass by Spoofing in GitLab
21Monitor
CVE-2024-152564 days apartAuthentication Bypass Using an Alternate Path or Channel in GitLab
21Monitor

Bug bounty scope

GitLabHackerOne · paid

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

TR-24-0354 · Apr 26, 2024(GitLab Güvenlik Bildirimi)

All national notices →

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: none
Availability: high · the service can be disrupted

Attack vector: Network
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: None
Availability impact: High

Weakness class (CWE)

CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

nvd-primary

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

The bug in code

The whole CWE-22 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const file = path.join(ROOT, req.query.name);
2res.sendFile(file);

Fixed

1const file = path.resolve(ROOT, req.query.name);
2if (!file.startsWith(ROOT + path.sep)) {
3  return res.sendStatus(400);
4}
5res.sendFile(file);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

Fix✗ → ✓Sep 28, 2026, 10:10 PM UTC

For records you follow, these changes also arrive as notifications. →

References

hackerone.com/reports/2401952

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records