# CVE-2020-4053: Path Traversal in Helm Plugin Archive

> A malicious plugin author can exploit path traversal in Helm to copy files outside the intended directory during plugin installation.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 16 Jun 2020
- **Updated:** 4 Aug 2024
- **Also known as:** BIT-helm-2020-4053, GHSA-qq3j-xp49-j73f

## What is CVE-2020-4053?

CVE-2020-4053 is a low-severity path traversal vulnerability in The Helm Project Helm, published on 16 Jun 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

In Helm greater than or equal to 3.0.0 and less than 3.2.4, a path traversal attack is possible when installing Helm plugins from a tar archive over HTTP. It is possible for a malicious plugin author to inject a relative path into a plugin archive, and copy a file outside of the intended directory. This has been fixed in 3.2.4.

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

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

3 open source packages ship an affected version, including helm.sh/helm/v3 and helm. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `helm.sh/helm/v3` | Go | From 3.0.0 | 3.2.4 |
| `helm.sh/helm/v3` | Go | From 3.0.0 | 3.2.4 |
| `helm` | Bitnami | From 3.0.0 | 3.2.4 |

Products: Helm Helm.

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

Upgrade helm.sh/helm/v3 to 3.2.4 or later.

## Is CVE-2020-4053 being exploited?

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

## Other vulnerabilities in The Helm Project Helm

- [CVE-2019-18658](https://insights.sbomify.com/CVE-2019-18658/): Helm Unsafe Link Following (critical 9.8)
- [CVE-2019-1010275](https://insights.sbomify.com/CVE-2019-1010275/): Helm Improper Certificate Validation (critical 9.8)
- [CVE-2019-25210](https://insights.sbomify.com/CVE-2019-25210/): Information disclosure in n/a (critical 9.1)
- [CVE-2025-53547](https://insights.sbomify.com/CVE-2025-53547/): Helm Chart Dependency Updating With Malicious Chart.yaml Content And Symlink Can Lead To Code Execution (high 8.5)
- [CVE-2020-11013](https://insights.sbomify.com/CVE-2020-11013/): lookup Function Information Discolosure in Helm (high 8.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-4053 is a low-severity path traversal vulnerability in The Helm Project Helm, published on 16 Jun 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-4053 in the wild and no public exploit code.

Affected packages and fixed versions:
- helm.sh/helm/v3 (Go): affected from 3.0.0; fixed in 3.2.4
- helm.sh/helm/v3 (Go): affected from 3.0.0; fixed in 3.2.4
- helm (Bitnami): affected from 3.0.0; fixed in 3.2.4

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-4053/ (Markdown: https://insights.sbomify.com/CVE-2020-4053/index.md)
```

## Sources

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

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