Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹 Go

GHSA-m54r-vrmv-hw33

LOW

GHSA-m54r-vrmv-hw33 is a low-severity (CVSS 3.4) Improper Input Validation vulnerability in helm.sh/helm/v3. O3 Security confirms whether GHSA-m54r-vrmv-hw33 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Improper Sanitizing of plugin names in helm

Also known asBIT-helm-2020-15186CVE-2020-15186
Published
May 24, 2021
Updated
Jul 8, 2026
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed

Blast Radius

2 pkgs affected
🐹helm.sh/helm/v3🐹helm.sh/helm

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Impact

Security researchers at Trail of Bits discovered that plugin names are not sanitized properly. As a result, a malicious plugin author could use characters in a plugin name that would result in unexpected behavior, such as duplicating the name of another plugin or spoofing the output to helm --help.

Specific Go Packages Affected

helm.sh/helm/v3/pkg/plugin

Patches

This issue has been patched in Helm 3.3.2.

Workarounds

Do not install untrusted Helm plugins. Examine the name field in the plugin.yaml file for a plugin, looking for characters outside of the [a-zA-Z0-9._-] range.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
🐹Gohelm.sh/helm/v33.0.0&&< 3.3.23.3.2
🐹Gohelm.sh/helmall versions2.16.11

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for helm.sh/helm/v3. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update helm.sh/helm/v3 to 3.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m54r-vrmv-hw33 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-m54r-vrmv-hw33 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-m54r-vrmv-hw33. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact Security researchers at Trail of Bits discovered that plugin names are not sanitized properly. As a result, a malicious plugin author could use characters in a plugin name that would result in unexpected behavior, such as duplicating the name of another plugin or spoofing the output to `helm --help`. ### Specific Go Packages Affected helm.sh/helm/v3/pkg/plugin ### Patches This issue has been patched in Helm 3.3.2. ### Workarounds Do not install untrusted Helm plugins. Examine the `name` field in the `plugin.yaml` file for a plugin, looking for characters outside of the [a-zA-Z
O3 Security · Impact-Aware SCA

Is GHSA-m54r-vrmv-hw33 in your dependencies?

O3 detects GHSA-m54r-vrmv-hw33 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.