Advisory record · GHSA-9vp5-m38w-j776

Aliases are never checked in helm

CVSS 3.7 LowEPSS 0.010 · 64th percentile

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

PackageEcosystemAffectedFixed in
helm.sh/helm/v3Go>=3.0.0, <3.3.23.3.2
helm.sh/helmGo<2.16.112.16.11
Identifiers
GHSA-9vp5-m38w-j776 · BIT-helm-2020-15184 · CVE-2020-15184
Weakness (CWE)
CWE-20 · CWE-74
Published
24 May 2021
Updated
8 Jul 2026

Machine-written summary

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

The Go packages helm.sh/helm/v3 (versions 3.0.0 before 3.3.2) and helm.sh/helm (versions before 2.16.11) fail to sanitize the alias field in Chart.yaml, so unwanted information can be injected into a chart. The source gives few details on the attacker's required access. Upgrade helm.sh/helm/v3 to 3.3.2 or helm.sh/helm to 2.16.11. If you cannot upgrade, manually review the dependencies field of untrusted charts to confirm that alias values contain no newlines or path characters.

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

ScoreRatingCVSSVectorSource
3.7 Low 3.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.010, the 64th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:05 UTC First seen by agentprime
  2. 31 Oct 2026, 15:05 UTC Confirmed by OSV

Sources

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.