Repository credentials passed to alternate domain in helm.sh/helm/v3
Published 15 Jul 2022 · Updated 4 Feb 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.6.1
- Fixed in
- 3.6.1
go get helm.sh/helm/v3@v3.6.1Details
The username and password credentials associated with a Helm repository can be passed to another domain referenced by that Helm repository.
If the index.yaml for a Helm repository is hosted on one domain and references a chart archive on a different domain, Helm will provide the credentials for the index.yaml's domain when fetching those archives.
Is GO-2022-0384 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-2026-35206Helm Chart extraction output directory collapse via Chart.yaml name dot-segment in helm.sh/helm · 24 Jul 2026
- MediumCVE-2026-35206Helm Chart extraction output directory collapse via `Chart.yaml` name dot-segment · 10 Apr 2026
- 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
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.