Is helm.sh/helm 2.1 vulnerable?
Go · 4 releases from 2.1.0 to 2.1.3 · latest helm.sh/helm is 2.17.0+incompatible · checked 18 Nov 2026
Yes: 12 known advisories
Yes. helm.sh/helm 2.1.3, the last 2.1 release, is affected by 12 known security advisories (2 critical, 1 medium, 9 low), including CVE-2019-18658, CVE-2019-1010275, CVE-2019-1000008. At least one has no fixed release yet.
Is your project on an affected helm.sh/helm?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting helm.sh/helm 2.1.3
Helm May Panic Due To Incorrect YAML Content in helm.sh/helm
- Affected
- All versions
- Fixed in
- No fix released
Helm Charts with Specific JSON Schema Values Can Cause Memory Exhaustion in helm.sh/helm
- Affected
- All versions
- Fixed in
- No fix released
Helm Improper Certificate Validation in helm.sh/helm
- Affected
- <2.7.2+incompatible
- Fixed in
- 2.7.2+incompatible
Helm Unsafe Link Following in helm.sh/helm
- Affected
- >=2.0.0+incompatible <2.15.2+incompatible
- Fixed in
- 2.15.2+incompatible
Helm Path Traversal in helm.sh/helm
- Affected
- >=2.0.0+incompatible <2.12.2+incompatible
- Fixed in
- 2.12.2+incompatible
Helm Unsafe Link Following
- Affected
- >=2.0.0 <2.15.2
- Fixed in
- 2.15.2
Helm Improper Certificate Validation
- Affected
- <2.7.2
- Fixed in
- 2.7.2
Helm Path Traversal
- Affected
- >=2.0.0 <2.12.2
- Fixed in
- 2.12.2
plugin.yaml file allows for duplicate entries in helm
- Affected
- >=2.0.0 <2.16.11
- Fixed in
- 2.16.11
Improper Sanitizing of plugin names in helm
- Affected
- <2.16.11
- Fixed in
- 2.16.11
Repository index file allows for duplicates of the same chart entry in helm
- Affected
- <2.16.11
- Fixed in
- 2.16.11
Aliases are never checked in helm
- Affected
- <2.16.11
- Fixed in
- 2.16.11
Every helm.sh/helm 2.1.x release
Affected: 2.1.0 to 2.1.3. Latest helm.sh/helm: 2.17.0+incompatible.
| Version | Known advisories |
|---|---|
| helm.sh/helm 2.1.3 | CVE-2025-55198, CVE-2025-55199, CVE-2019-1010275, CVE-2019-18658, CVE-2019-1000008, CVE-2019-18658, CVE-2019-1010275, CVE-2019-1000008, CVE-2020-15187, CVE-2020-15186, CVE-2020-15185, CVE-2020-15184 |
| helm.sh/helm 2.1.2 | CVE-2025-55198, CVE-2025-55199, CVE-2019-1010275, CVE-2019-18658, CVE-2019-1000008, CVE-2019-18658, CVE-2019-1010275, CVE-2019-1000008, CVE-2020-15187, CVE-2020-15186, CVE-2020-15185, CVE-2020-15184 |
| helm.sh/helm 2.1.1 | CVE-2025-55198, CVE-2025-55199, CVE-2019-1010275, CVE-2019-18658, CVE-2019-1000008, CVE-2019-18658, CVE-2019-1010275, CVE-2019-1000008, CVE-2020-15187, CVE-2020-15186, CVE-2020-15185, CVE-2020-15184 |
| helm.sh/helm 2.1.0 | CVE-2025-55198, CVE-2025-55199, CVE-2019-1010275, CVE-2019-18658, CVE-2019-1000008, CVE-2019-18658, CVE-2019-1010275, CVE-2019-1000008, CVE-2020-15187, CVE-2020-15186, CVE-2020-15185, CVE-2020-15184 |
Which of your client projects are still on helm.sh/helm 2.1?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact helm.sh/helm version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other helm.sh/helm versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Go registry. Refreshed daily.