Repository index file allows for duplicates of the same chart entry in helm

Exploitation

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

CVSS

2.2 · CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:N

EPSS

• CVE-2020-15185: 0.88% estimated exploitation activity in the next 30 days; percentile 59.24 (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.

Impact During a security audit of Helm's code base, security researchers at Trail of Bits identified a bug in which the 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). Specific Go Packages Affected helm.sh/helm/v3/pkg/repo Patches This issue has been patched in Helm 3.3.2 and 2.16.11 Workarounds - do not install charts from repositories you do not trust - fetch charts using a secure channel of communication (such as TLS) - use helm pull to fetch the chart, then review the chart’s content (either manually, or with helm verify if it has been signed) to ensure it has not been tampered with - manually review the index file in the Helm repository cache before installing software.

Published by the source

24 May 2021, 16:57 UTC

Last modified by the source

2 Oct 2023, 13:35 UTC

Source last checked

26 Oct 2026, 14:59 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-jm56-5h66-w453

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

# Patch Next advisory brief: CVE-2020-15185

Advisory: Repository index file allows for duplicates of the same chart entry in helm
IDs: CVE-2020-15185, GHSA-jm56-5h66-w453
Record: https://patchnext.com/advisories/cve-2020-15185 (revision 1, source checked 26 Oct 2026, 14:59 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.2)
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.3.2; helm.sh/helm 2.16.11. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go helm.sh/helm/v3: affected >= 3.0.0, < 3.3.2; fixed in 3.3.2
- Go helm.sh/helm: affected < 2.16.11; fixed in 2.16.11

## Suggested inspection (read-only)
- Go helm.sh/helm/v3: check the installed version with your package manager.
- Go helm.sh/helm: 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, helm.sh/helm.
- 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-jm56-5h66-w453 (GitHub-reviewed advisory GHSA-jm56-5h66-w453 lists affected ranges: Go helm.sh/helm/v3 >=3.0.0 =0 <2.16.11)

Commands are suggestions: review each one before running it.