Description
In Helm before versions 2.16.11 and 3.3.2, a Helm repository can contain duplicates of the same chart, with the last one always used. If a repository is compromised, this lowers the level of access that an attacker needs to inject a bad chart into a repository. To perform this attack, an attacker must have write access to the index file (which can occur during a MITM attack on a non-SSL connection). This issue has been patched in Helm 3.3.2 and 2.16.11. A possible workaround is to manually review the index file in the Helm repository cache before installing software.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| helm | helm | >= 2.0.0, < 2.16.11, >= 3.0.0, < 3.3.2 | — |
Fixed in Linux distributions
Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.
SUSE
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| SLES 15 SP1 | kubernetes | 1.17.13-4.21.2 | SUSE-SU-2020:3760-1 |
Affected packages
| Ecosystem | Package | Affected | Fixed | Record |
|---|---|---|---|---|
| Go | helm.sh/helm | < 2.16.11 | 2.16.11 | GHSA-jm56-5h66-w453 |
| Go | helm.sh/helm/v3 | >= 3.0.0, < 3.3.2 | 3.3.2 | GHSA-jm56-5h66-w453 |
Advisories 1
- SUSE-SU-2020:3760-1 Security changes in Kubernetes, etcd, and helm; Bugfix in cri-o package SUSE / openSUSE Security Updates · Feb 4, 2026