# Improper Sanitizing of plugin names in helm

Advisory record · `GHSA-m54r-vrmv-hw33`

- **Identifiers:** `GHSA-m54r-vrmv-hw33` · `BIT-helm-2020-15186` · `CVE-2020-15186`
- **State:** Confirmed
- **Severity:** CVSS 3.4 Low
- **Critical:** No
- **Weakness (CWE):** [CWE-20](https://cwe.mitre.org/data/definitions/20.html) · [CWE-74](https://cwe.mitre.org/data/definitions/74.html)
- **Tags:** [Other injection](https://agentprime.io/advisories/tag/injection.md) · [CWE-20](https://agentprime.io/advisories/tag/cwe-20.md)
- **Published:** 24 May 2021
- **Updated:** 8 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 24 May 2021, 16:57 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `helm.sh/helm/v3` (Go): affected `>=3.0.0, <3.3.2`; fixed in `3.3.2`
- `helm.sh/helm` (Go): affected `<2.16.11`; fixed in `2.16.11`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Helm (helm.sh/helm/v3 from 3.0.0 before 3.3.2, and helm.sh/helm before 2.16.11) does not properly sanitize plugin names. A malicious plugin author could use special characters in a plugin name to duplicate another plugin's name or spoof the output of helm --help. Upgrade to Helm 3.3.2 or 2.16.11; until then, avoid installing untrusted plugins and check plugin.yaml name fields for characters outside a-z, A-Z, 0-9, period, underscore, and hyphen.

Written 6 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 3.4 Low, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:N/I:L/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0096, the 62nd percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:05 UTC: First seen by agentprime
- 31 Oct 2026, 15:05 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-m54r-vrmv-hw33)

## Sources

- [GitHub Advisory Database: GHSA-m54r-vrmv-hw33](https://github.com/advisories/GHSA-m54r-vrmv-hw33)
- [OSV: GHSA-m54r-vrmv-hw33](https://osv.dev/vulnerability/GHSA-m54r-vrmv-hw33)
- <https://github.com/helm/helm/security/advisories/GHSA-m54r-vrmv-hw33>
- <https://nvd.nist.gov/vuln/detail/CVE-2020-15186>
- <https://github.com/helm/helm/commit/809e2d999e2c33e20e77f6bff30652d79c287542>
- <https://github.com/helm/helm/commit/c8d6b01d72c9604e43ee70d0d78fadd54c2d8499>
- <https://github.com/helm/helm>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-m54r-vrmv-hw33>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-m54r-vrmv-hw33/>. Everything for agents: <https://agentprime.io/llms.txt>.
