LowGO-2026-5435BIT-helm-2026-35206CVE-2026-35206GHSA-hr2v-4r36-88hr
Helm Chart extraction output directory collapse via Chart.yaml name dot-segment in helm.sh/helm
Published 24 Jul 2026 · Updated 21 Aug 2026
Is your project on an affected helm.sh/helm/v3?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- <3.20.2
- Fixed in
- 3.20.2
Update to the fixed version for your release line, for example:
go get helm.sh/helm/v3@v3.20.2Details
Helm Chart extraction output directory collapse via Chart.yaml name dot-segment in helm.sh/helm
Is GO-2026-5435 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/v3, and gives you the command that fixes it.
More advisories for helm.sh/helm/v3
- LowCVE-2025-55198Helm May Panic Due To Incorrect YAML Content in helm.sh/helm · 18 Aug 2025
- LowCVE-2025-55199Helm Charts with Specific JSON Schema Values Can Cause Memory Exhaustion in helm.sh/helm · 18 Aug 2025
- MediumCVE-2025-55198Helm May Panic Due To Incorrect YAML Content · 14 Aug 2025
- MediumCVE-2025-55199Helm Charts with Specific JSON Schema Values Can Cause Memory Exhaustion · 14 Aug 2025
- LowCVE-2025-53547Helm vulnerable to Code Injection through malicious chart.yaml content in helm.sh/helm · 21 Jul 2025
- HighCVE-2025-53547Helm vulnerable to Code Injection through malicious chart.yaml content · 8 Jul 2025
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.