How severe is CVE-2024-25620?

CVE-2024-25620 has a CVSS score of 6.4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2024-25620?

CVE-2024-25620 affects the following packages: helm.sh/helm/v3 (Go). Ecosystems affected: Go.

How do I fix CVE-2024-25620?

Update helm.sh/helm/v3 to 3.14.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-25620 is resolved across your whole dependency graph.

How do I detect CVE-2024-25620 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for helm.sh/helm/v3, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2024-25620 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is CVE-2024-25620 actively exploited in the wild?

No public exploit code has been indexed for CVE-2024-25620 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2024-25620?

CVE-2024-25620 has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 47th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2024-25620?

CVE-2024-25620 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2024-25620 published, and has it been updated?

CVE-2024-25620 was published on February 14, 2024 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

MEDIUM severity

CVE-2024-25620 — helm

MEDIUMFix: helm/helm@0d0f91d

CVE-2024-25620 is a medium-severity (CVSS 6.4) Path Traversal vulnerability in helm.sh/helm/v3. A fix is available for helm.sh/helm/v3 — see the affected versions and patch details below.

Dependency management path traversal in helm

Also known asBIT-helm-2024-25620GHSA-v53g-5gjp-272rGO-2024-2554

Published

Feb 14, 2024

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-25620.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs47th percentile — riskier than 47% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐹helm.sh/helm/v3

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

A Helm contributor discovered a path traversal vulnerability when Helm saves a chart including at download time.

Impact

When either the Helm client or SDK is used to save a chart whose name within the Chart.yaml file includes a relative path change, the chart would be saved outside its expected directory based on the changes in the relative path. The validation and linting did not detect the path changes in the name.

Patches

This issue has been resolved in Helm v3.14.1.

Workarounds

Check all charts used by Helm for path changes in their name as found in the Chart.yaml file. This includes dependencies.

Credits

Disclosed by Dominykas Blyžė at Nearform Ltd.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`helm.sh/helm/v3`	all versions	3.14.1`go get helm.sh/helm/v3@v3.14.1`

Affected Products

1 product · 1 configurations

Application

helmhelm

< 3.14.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for helm.sh/helm/v3, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update helm.sh/helm/v3 to 3.14.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-25620 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Product	Fixed in	Advisory
Red Hat Advanced Cluster Management for Kubernetes 2.9 for RHEL 8	`rhacm2/acm-governance-policy-addon-controller-rhel8:v2.9.3-9`	RHSA-2024:1328
Red Hat OpenShift Container Platform 4.15	`openshift4/ose-olm-rukpak-rhel8:v4.15.0-202403081338.p0.g5b09cd4.assembly.stream.el8`	RHSA-2024:1255
Red Hat OpenShift Container Platform 4.15	`openshift4/ose-azure-cluster-api-controllers-rhel9:v4.15.0-202405130639.p0.g0584f1f.assembly.stream.el9`	RHSA-2024:2865
Red Hat OpenShift Container Platform 4.17	`openshift4/ose-console-rhel9:v4.17.0-202409130504.p0.g5bbc956.assembly.stream.el9`	RHSA-2024:3718
Red Hat OpenShift GitOps 1.11	`openshift-gitops-1/argocd-rhel8:v1.11.6-2`	RHSA-2024:4626
Red Hat OpenShift GitOps 1.12	`openshift-gitops-1/argocd-rhel8:v1.12.4-5`	RHSA-2024:4163

Frequently Asked Questions

A Helm contributor discovered a path traversal vulnerability when Helm saves a chart including at download time. ### Impact When either the Helm client or SDK is used to save a chart whose name within the `Chart.yaml` file includes a relative path change, the chart would be saved outside its expected directory based on the changes in the relative path. The validation and linting did not detect the path changes in the name. ### Patches This issue has been resolved in Helm v3.14.1. ### Workarounds Check all charts used by Helm for path changes in their name as found in the `Chart.yaml` fil