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
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
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2024-25620 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,636 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
helm.sh/helm/v3Real-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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | helm.sh/helm/v3 | all versions | 3.14.1go get helm.sh/helm/v3@v3.14.1 |
Detection & mitigation playbook
Open-source dependencyDetect
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
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2024-25620 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2024-25620. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
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.
| 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
Is CVE-2024-25620 in your dependencies?
O3 Security finds CVE-2024-25620 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.