plugin.yaml file allows for duplicate entries in helm

Exploitation

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

CVSS

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

EPSS

• CVE-2020-15187: 1.52% estimated exploitation activity in the next 30 days; percentile 74.57 (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, Helm maintainers identified a bug in which a Helm plugin can contain duplicates of the same entry, with the last one always used. If a plugin is compromised, this lowers the level of access that an attacker needs to modify a plugin's install hooks, causing a local execution attack. To perform this attack, an attacker must have write access to the git repository or plugin archive (.tgz) while being downloaded (which can occur during a MITM attack on a non-SSL connection). Patches This issue has been patched in Helm 2.16.11 and Helm 3.3.2. Workarounds Make sure to install plugins using a secure connection protocol like SSL.

Published by the source

24 May 2021, 16:57 UTC

Last modified by the source

29 May 2025, 22:59 UTC

Source last checked

26 Oct 2026, 15:09 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-c52f-pq47-2r9j

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

# Patch Next advisory brief: CVE-2020-15187

Advisory: plugin.yaml file allows for duplicate entries in helm
IDs: CVE-2020-15187, GHSA-c52f-pq47-2r9j
Record: https://patchnext.com/advisories/cve-2020-15187 (revision 1, source checked 26 Oct 2026, 15:09 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 3.0)
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.0.0, < 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-c52f-pq47-2r9j (GitHub-reviewed advisory GHSA-c52f-pq47-2r9j lists affected ranges: Go helm.sh/helm/v3 >=3.0.0 =2.0.0 <2.16.11)

Commands are suggestions: review each one before running it.