CVE-2020-15184Low· 3.7▾ SunlitAliases are never checked in helm
▾ Sunlit zone — Low / medium · no exploitation signal
impact 20.4 · likelihood 0.2 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Jul 9.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
Last analysed / modified upstream
1.0%
During a security audit of Helm's code base, security researchers at Trail of Bits identified a bug in which the alias field on a Chart.yaml is not properly sanitized. This could lead to the injection of unwanted information into a chart.
This issue has been patched in Helm 3.3.2 and 2.16.11
helm.sh/helm/v3/pkg/chartutil
Manually review the dependencies field of any untrusted chart, verifying that the alias field is either not used, or (if used) does not contain newlines or path characters.
helm.sh/helm/v3 >= 3.0.0, < 3.3.2helm.sh/helm < 2.16.11Upgrade to a patched release:
helm.sh/helm/v3 3.3.2helm.sh/helm 2.16.11Connected by shared product, vendor, weakness, or advisory.
CVE-2020-15187Low· 3.0plugin.yaml file allows for duplicate entries in helm
CVE-2022-36055Medium· 6.5Helm Vulnerable to denial of service through string value parsing
CVE-2025-32387Medium· 6.5Helm Allows A Specially Crafted JSON Schema To Cause A Stack Overflow
CVE-2025-32386Medium· 6.5Helm Allows A Specially Crafted Chart Archive To Cause Out Of Memory Termination
CVE-2020-15186Low· 3.4Improper Sanitizing of plugin names in helm
CVE-2020-15185Low· 2.2Repository index file allows for duplicates of the same chart entry in helm