CVE-2020-26405 Path traversal in GitLab CE/EE
An attacker can exploit a path traversal flaw in GitLab's package upload feature to save packages in arbitrary locations on the server.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2020-26405?
CVE-2020-26405 is a high-severity path traversal vulnerability in Gitlab Gitlab, published on 17 Nov 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
Path traversal vulnerability in package upload functionality in GitLab CE/EE starting from 12.8 allows an attacker to save packages in arbitrary locations. Affected versions are >=12.8, <13.3.9,>=13.4, <13.4.5,>=13.5, <13.5.2.
Weakness: CWE-22
Which versions are affected by CVE-2020-26405?
1 open source package ship an affected version, including gitlab. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
gitlab Bitnami | All versions | 13.5.2 |
Products include Gitlab Gitlab.
How do I fix CVE-2020-26405?
Upgrade gitlab to 13.5.2 or later.
Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.
Is CVE-2020-26405 being exploited?
There is no known exploitation of CVE-2020-26405 in the wild and no public exploit code.
Other vulnerabilities in Gitlab Gitlab
- CVE-2026-97229 GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound
- CVE-2026-85706 GitLab Community Edition and Enterprise Edition Path Traversal
- CVE-2023-7028 GitLab Community and Enterprise Editions Improper Access Control
- CVE-2021-22205 GitLab Community and Enterprise Editions Remote Code Execution
- CVE-2021-39935 GitLab Community and Enterprise Editions Server-Side Request Forgery (SSRF)
Sources
Also known as BIT-gitlab-2020-26405, GHSA-jg4r-vvqm-988m.