Helm Chart extraction output directory collapse via `Chart.yaml` name dot-segment
Published 10 Apr 2026 · Updated 10 Sept 2026
Is your project on an affected helm.sh/helm/v4?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- <4.1.4
- Fixed in
- 4.1.4
go get helm.sh/helm/v4@v4.1.4- Affected
- <3.20.2
- Fixed in
- 3.20.2
go get helm.sh/helm/v3@v3.20.2Details
Helm is a package manager for Charts for Kubernetes. In Helm versions <=3.20.1 and <=4.1.3, a specially crafted Chart will cause helm pull --untar [chart URL | repo/chartname] to write the Chart's contents to the immediate output directory (as defaulted to the current working directory; or as given by the --destination and --untardir flags), rather than the expected output directory suffixed by the chart's name.
Impact
The bug enables writing the Chart's contents (unpackaged/untar'ed) to the output directory <output dir>/, instead of the expected <output dir>/<chart name>/, potentially overwriting the contents of the targeted directory.
Note: a chart name containing POSIX dot-dot, or dot-dot and slashes (as if to refer to parent directories) do not resolve beyond the output directory as designed.
Patches
This issue has been resolved in Helm v3.20.2 and v4.1.3
A Chart with an unexpected name (those specified to be "." or ".."), or a Chart name which results in a non-unique directory will be rejected.
Workarounds
Ensure the the name of the Chart does not comprise/contain POSIX pathname special directory references ie. dot-dot ("..") or dot ("."). In addition, ensuring that the pull --untar flag (or equivalent SDK option) refers to a unique/empty output directory prevents chart extraction from inadvertently overwriting existing files within the specified directory.
Credits
Oleh Konko @1seal
Is GHSA-hr2v-4r36-88hr in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected helm.sh/helm/v4, and gives you the command that fixes it.
More advisories for helm.sh/helm/v4
- LowCVE-2026-35205Helm's plugin verification fails open when .prov is missing, allowing unsigned plugin install in helm.sh/helm · 24 Jul 2026
- LowCVE-2026-35204Helm path traversal in plugin metadata version enables arbitrary file write outside Helm plugin directory in helm.sh/helm · 24 Jul 2026
- HighCVE-2026-35205Helm's plugin verification fails open when .prov is missing, allowing unsigned plugin install · 10 Apr 2026
- HighCVE-2026-35204Helm has a path traversal in plugin metadata version enables arbitrary file write outside Helm plugin directory · 10 Apr 2026
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.