# CVE-2020-10953: Path traversal in n/a

> An attacker can exploit a path traversal vulnerability in the NPM feature to read arbitrary files from the server.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Mar 2020
- **Updated:** 4 Aug 2024
- **Also known as:** BIT-gitlab-2020-10953, GHSA-ww9f-vr49-c3pf

## What is CVE-2020-10953?

CVE-2020-10953 is a high-severity path traversal vulnerability in Gitlab Gitlab, published on 27 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In GitLab EE 11.7 through 12.9, the NPM feature is vulnerable to a path traversal issue.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2020-10953?

1 open source package ship an affected version, including gitlab. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gitlab` | Bitnami | From 11.7.0 | 12.9.1 |

Products: Gitlab Gitlab.

## How do I fix CVE-2020-10953?

Upgrade gitlab to 12.9.1 or later.

## Is CVE-2020-10953 being exploited?

There is no known exploitation of CVE-2020-10953 in the wild and no public exploit code.

## Other vulnerabilities in Gitlab Gitlab

- [CVE-2026-97229](https://insights.sbomify.com/CVE-2026-97229/): GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound (critical 10.0, exploited in the wild)
- [CVE-2026-85706](https://insights.sbomify.com/CVE-2026-85706/): GitLab Community Edition and Enterprise Edition Path Traversal (critical 10.0, exploited in the wild)
- [CVE-2023-7028](https://insights.sbomify.com/CVE-2023-7028/): GitLab Community and Enterprise Editions Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2021-22205](https://insights.sbomify.com/CVE-2021-22205/): GitLab Community and Enterprise Editions Remote Code Execution (critical 10.0, exploited in the wild)
- [CVE-2021-39935](https://insights.sbomify.com/CVE-2021-39935/): GitLab Community and Enterprise Editions Server-Side Request Forgery (SSRF) (medium 6.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-10953 and fix it if it is affected.

What it is: CVE-2020-10953 is a high-severity path traversal vulnerability in Gitlab Gitlab, published on 27 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-10953 in the wild and no public exploit code.

Affected packages and fixed versions:
- gitlab (Bitnami): affected from 11.7.0; fixed in 12.9.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-10953/ (Markdown: https://insights.sbomify.com/CVE-2020-10953/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-10953
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-10953
- OSV: https://osv.dev/vulnerability/CVE-2020-10953

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-10953/
Summaries are generated and may contain mistakes; the official description above is the record.