Helm bug bounty programs
helm.sh Updated
Helm runs one public program: a Sorona bug bounty paying up to $1,500.
- Top reward
- $1,500
- Sorona
- Programs
- 1
- 1 pays cash
- Targets in scope
- 14
- 2 types
- Last change
- None yet
- Tracked since Nov 2026
Where to report
The one public program Helm runs.
| Program | Critical | High | Medium | Low | Top reward | Safe harbor | KYC | First response | Status |
|---|---|---|---|---|---|---|---|---|---|
|
Helm
Sorona · Bug bounty |
– | – | – | $100 | $1,500 | Partial | – | 3 days promised | Open |
-
- Critical
- –
- High
- –
- Medium
- –
- Low
- $100
- Safe harbor
- Partial
- First response
- 3 days promised
Amounts are the top reward per severity in the currency each program pays. First response is the platform's measured average when it publishes one, else what the policy promises.
What is in scope
14 targets. 6 excluded.
-
https://helm.sh
Web
-
Chart dependency resolution, the repository client, the index file it fetches and the lock file it writes
Products and areas
-
Chart hooks, their ordering and the resources they create outside the normal release
Products and areas
-
kubeconfig handling, the credentials Helm uses to talk to the cluster and the post-renderer hook that pipes manifests through an external command
Products and areas
-
OCI registry support end to end, covering pull, push, authentication, credential storage and the manifest handling in between
Products and areas
-
Provenance and signature verification: provenance files, the PGP path and helm verify
Products and areas
-
Release storage in Secrets or ConfigMaps, including what is written there and who in the namespace can read it
Products and areas
-
The chart loader and archive handling, covering tar extraction, entry names, symlinks and everything a .tgz can express about where a file should land
Products and areas
-
The Go template rendering engine as Helm configures it, and the whole sprig function set exposed to chart authors
Products and areas
-
The Helm Go SDK, which GitOps controllers embed rather than shelling out to the binary
Products and areas
-
The plugin system, plugin installation from a URL or a repository, and what an installed plugin can run
Products and areas
-
The published process asks for private reports to [email protected] and declares no boundary narrower than the Helm codebase. Everything below sits inside that
Products and areas
-
The release lifecycle commands, install, upgrade, rollback and uninstall, and the manifests each applies
Products and areas
-
Values handling: the merge order across files, --set, --set-string, --set-file and --set-json, and the parser behind each
Products and areas
No target matches. Try part of a host name, such as the company name.
Out of scope 6
Don't test these. A program can exclude a host another program covers; the program you report to decides.
-
A chart an operator installed knowingly with elevated RBAC or with hooks they reviewed
-
Argo CD, Flux and other tools that embed the SDK, each with its own security process
-
Kubernetes itself, the API server and the kubelet, all covered by a separate project with its own paid programme
-
The contents of third-party charts, which are the chart author's decision rather than a Helm defect
-
thehelm.com, an unrelated company that happens to share the name on Bugcrowd
-
Upstream Go libraries, unless Helm's own use of them is what makes the defect reachable
Recent changes
Reward and scope changes across every Helm program, newest first.
No changes recorded yet. New targets and reward moves show up here and in the RSS feed.
Recent CVEs
Published vulnerabilities in Helm products, from the NVD.
-
CVE-2026-63308 Medium
Helm through 4.2.3, fixed in commit ba6c9a2, contains a denial of service vulnerability in the Files.Lines template helper in pkg/engine/files.go that allows attackers to trigger an index out of range panic by including zero-length byte slices in chart files. Attackers can include empty files in Helm charts to cause deterministic render failures across template, install, upgrade, lint, and SDK Eng
-
CVE-2026-35206 Medium
Helm is a package manager for Charts for Kubernetes. In Helm versions <=3.20.1 and <=4.1.3, a specially crafted Chart will cause helm pull --untar [chart URL | repo/chartname] to write the Chart's contents to the immediate output directory (as defaulted to the current working directory; or as given by the --destination and --untardir flags), rather than the expected output directory suffixed by th
-
CVE-2026-35204 High
Helm is a package manager for Charts for Kubernetes. From 4.0.0 to 4.1.3, a specially crafted Helm plugin, when installed or updated, will cause Helm to write the contents of the plugin to an arbitrary filesystem location. To prevent this, validate that the plugin.yaml of the Helm plugin does not include a version: field containing POSIX dot-dot path separators ie. "/../". This vulnerability is fi
-
CVE-2026-35205 High
Helm is a package manager for Charts for Kubernetes. From 4.0.0 to 4.1.3, Helm will install plugins missing provenance (.prov file) when signature verification is required. This vulnerability is fixed in 4.1.4.
-
CVE-2025-55199 Medium
Helm is a package manager for Charts for Kubernetes. Prior to version 3.18.5, it is possible to craft a JSON Schema file in a manner which could cause Helm to use all available memory and have an out of memory (OOM) termination. This issue has been resolved in Helm 3.18.5. A workaround involves ensuring all Helm charts that are being loaded into Helm do not have any reference of $ref pointing to /
-
CVE-2025-55198 Medium
Helm is a package manager for Charts for Kubernetes. Prior to version 3.18.5, when parsing Chart.yaml and index.yaml files, an improper validation of type error can lead to a panic. This issue has been resolved in Helm 3.18.5. A workaround involves ensuring YAML files are formatted as Helm expects prior to processing them with Helm.
-
CVE-2025-53547 High
Helm is a package manager for Charts for Kubernetes. Prior to 3.18.4, a specially crafted Chart.yaml file along with a specially linked Chart.lock file can lead to local code execution when dependencies are updated. Fields in a Chart.yaml file, that are carried over to a Chart.lock file when dependencies are updated and this file is written, can be crafted in a way that can cause execution if that
-
CVE-2025-32386 Medium
Helm is a tool for managing Charts. A chart archive file can be crafted in a manner where it expands to be significantly larger uncompressed than compressed (e.g., >800x difference). When Helm loads this specially crafted chart, memory can be exhausted causing the application to terminate. This issue has been resolved in Helm v3.17.3.
About this page
This page gathers every public program listed under helm.sh: platform programs, self-hosted policies and security.txt contacts. Each program's own policy decides what is in scope and what it pays; check it before you test.
Something wrong or missing? Report a correction.