helm.sh/helm vulnerabilities
- Registry
- Go
- Latest
- 2.17.0+incompatible
12 known advisories
The latest version, 2.17.0+incompatible, is affected by 2 of them.
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
Security advisories for helm.sh/helm
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
Is your helm.sh/helm version vulnerable?
Which of your client projects still run an old helm.sh/helm?
NPMscan reads the go.mod in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Go packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Go registry.