Helm dependency management path traversal

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.4 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

EPSS

• CVE-2024-25620: 0.57% estimated exploitation activity in the next 30 days; percentile 47.08 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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.

Published by the source

15 Feb 2024, 15:34 UTC

Last modified by the source

24 Mar 2026, 05:08 UTC

Source last checked

26 Oct 2026, 15:18 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-v53g-5gjp-272r

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-25620

Advisory: Helm dependency management path traversal
IDs: CVE-2024-25620, GHSA-v53g-5gjp-272r
Record: https://patchnext.com/advisories/cve-2024-25620 (revision 1, source checked 26 Oct 2026, 15:18 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: helm.sh/helm/v3 3.14.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go helm.sh/helm/v3: affected <= 3.14.0; fixed in 3.14.1

## Suggested inspection (read-only)
- Go helm.sh/helm/v3: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on helm.sh/helm/v3.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-v53g-5gjp-272r (GitHub-reviewed advisory GHSA-v53g-5gjp-272r lists affected ranges: Go helm.sh/helm/v3 >=0 <=3.14.0)

Commands are suggestions: review each one before running it.