Skip to content
bugbounty.fyi
Get paid to secure open source 475 paid open-source programs on Sorona, up to $1M Perk Low bugs: $100 or 1 mo Claude Max

Also on Patchstack. All 476 paid open-source programs

Try

Highest paying Newly launched Paid without KYC Full safe harbor
All results

About this site

Helm

Bug bounty on Sorona helm.sh

Accepting reports open-source
Go to program Website
Top reward
$1,500
Top severity paid
Critical
Assets in scope
14
Public CVEs
30
Last change
No changes yet

At a glance

What to know before you start testing.

Pays from $1,500
for critical bugs.
Report on Sorona
Submit through the program page.
Partial safe harbor
Some legal protection; read the terms.
Replies within 3 days
As the policy promises.
Publish after a fix
Coordinate the timing with the company.

Rewards

What Sorona lists as the payout for each severity.

Severity Reward
Critical $1,500+
High $700+
Medium $300+
Low $100 $100 / 1 month Claude Max
Response
Within 3 days acknowledgement comes within three business days
Safe harbor
Partial Sorona will not pursue legal action against you for good-faith research submitted to us in line with this policy. We cannot speak for the upstream project, its vendor, or any third party, and we do not grant authorization on their behalf.

Summarised with AI from the program policy on Sorona, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

14 assets you may test, 6 excluded.

Web 1

  • https://helm.sh

Products and areas 13

  • Chart dependency resolution, the repository client, the index file it fetches and the lock file it writes
  • Chart hooks, their ordering and the resources they create outside the normal release
  • kubeconfig handling, the credentials Helm uses to talk to the cluster and the post-renderer hook that pipes manifests through an external command
  • OCI registry support end to end, covering pull, push, authentication, credential storage and the manifest handling in between
  • Provenance and signature verification: provenance files, the PGP path and helm verify
  • Release storage in Secrets or ConfigMaps, including what is written there and who in the namespace can read it
  • The chart loader and archive handling, covering tar extraction, entry names, symlinks and everything a .tgz can express about where a file should land
  • The Go template rendering engine as Helm configures it, and the whole sprig function set exposed to chart authors
  • The Helm Go SDK, which GitOps controllers embed rather than shelling out to the binary
  • The plugin system, plugin installation from a URL or a repository, and what an installed plugin can run
  • The published process asks for private reports to [email protected] and declares no boundary narrower than the Helm codebase. Everything below sits inside that
  • The release lifecycle commands, install, upgrade, rollback and uninstall, and the manifests each applies
  • Values handling: the merge order across files, --set, --set-string, --set-file and --set-json, and the parser behind each
Out of scope (6)
  • 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

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Sorona's policy.

While testing

  • Submit through sorona.xyz.
  • Report privately to the address on the policy page , the address helm.sh publishes.
  • Do not file this at the Bugcrowd programme named Helm.
  • Do not file it at the Kubernetes HackerOne programme either.
  • Say whether the finding needs a malicious chart, a malicious chart repository or a malicious registry.
  • State whether it reproduces through the Helm CLI, the Go SDK or both.
  • Hold detail until the advisory and the fixed release are out.

Summarised with AI from the program policy on Sorona, read 12 Nov 2026, and checked word for word against it. Read the original

Changes

Tracked since 11 Nov 2026. Last checked 1 hour ago.

No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.

Public CVEs

Published vulnerabilities in this vendor's products, from the NVD.

Search NVD
CVESeverityPublished
CVE-2026-63308 Medium 5.3 17 Jul 2026
CVE-2026-35206 Medium 4.8 9 Apr 2026
CVE-2026-35204 High 8.4 9 Apr 2026
CVE-2026-35205 High 8.4 9 Apr 2026
CVE-2025-55199 Medium 6.5 14 Aug 2025
CVE-2025-55198 Medium 6.5 14 Aug 2025
CVE-2025-53547 High 8.5 8 Jul 2025
CVE-2025-32386 Medium 6.5 9 Apr 2025
CVE-2025-32387 Medium 6.5 9 Apr 2025
CVE-2019-25210 Medium 6.5 3 Mar 2024
CVE-2024-26147 High 7.5 21 Feb 2024
CVE-2024-25620 Medium 6.4 15 Feb 2024
CVE-2023-25165 Medium 4.3 8 Feb 2023
CVE-2022-23524 Medium 5.3 15 Dec 2022
CVE-2022-23525 Medium 5.3 15 Dec 2022
CVE-2022-23526 Medium 5.3 15 Dec 2022
CVE-2022-36049 High 7.7 7 Sep 2022
CVE-2022-36055 Medium 6.5 1 Sep 2022
CVE-2021-32690 Medium 6.8 16 Jun 2021
CVE-2021-21303 Medium 5.9 5 Feb 2021
CVE-2020-15186 Low 3.4 17 Sep 2020
CVE-2020-15187 Low 3.0 17 Sep 2020
CVE-2020-15185 Low 2.2 17 Sep 2020
CVE-2020-15184 Low 3.7 17 Sep 2020
CVE-2020-4053 Low 3.7 16 Jun 2020
CVE-2020-11013 High 8.5 24 Apr 2020
CVE-2019-18658 Critical 9.8 12 Nov 2019
CVE-2019-1010275 Critical 9.8 17 Jul 2019
CVE-2019-1000008 Medium 6.5 4 Feb 2019
CVE-2019-1000009 Medium 6.5 4 Feb 2019

Original policy

Copied from sorona.xyz on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.

Skip to content What this pays This project runs no bounty of its own. sorona.xyz pays you directly on qualified, reproduced findings. Severity │ sorona.xyz pays Critical │ $1,500+ High │ $700+ Medium │ $300+ Low │ $100 / 1 month Claude Max Submit a vulnerability CVE history 5 Last 12 months 24 Lifetime Path traversal 35 % Supply chain 25 % Template injection 25 % Info disclosure 15 % Latest advisories Loading the feed Overview Helm is how applications get deployed to Kubernetes. Charts are the standard packaging format, and Helm runs inside the CI/CD and GitOps toolchains that push to production clusters, Argo CD and Flux among them. It unpacks archives and renders templates from sources the operator did not write, then applies the result with whatever cluster credentials the operator holds. A chart-parsing or template defect therefore executes in a pipeline that frequently has cluster-admin. Helm sits in its own GitHub organisation, outside the paid Kubernetes bug bounty, and its CNCF security list offers no reward. sorona.xyz pays you directly on qualified, reproduced findings. In scope The published process asks for private reports to [email protected] and declares no boundary narrower than the Helm codebase. Everything below sits inside that The chart loader and archive handling, covering tar extraction, entry names, symlinks and everything a .tgz can express about where a file should land The Go template rendering engine as Helm configures it, and the whole sprig function set exposed to chart authors Values handling: the merge order across files, --set , --set-string , --set-file and --set-json , and the parser behind each Chart dependency resolution, the repository client, the index file it fetches and the lock file it writes OCI registry support end to end, covering pull, push, authentication, credential storage and the manifest handling in between Provenance and signature verification: provenance files, the PGP path and helm verify The release lifecycle commands, install , upgrade , rollback and uninstall , and the manifests each applies Release storage in Secrets or ConfigMaps, including what is written there and who in the namespace can read it Chart hooks, their ordering and the resources they create outside the normal release The plugin system, plugin installation from a URL or a repository, and what an installed plugin can run The Helm Go SDK, which GitOps controllers embed rather than shelling out to the binary kubeconfig handling, the credentials Helm uses to talk to the cluster and the post-renderer hook that pipes manifests through an external command Out of scope 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 Argo CD, Flux and other tools that embed the SDK, each with its own security process A chart an operator installed knowingly with elevated RBAC or with hooks they reviewed 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 Most-valued findings Path traversal on chart unpack, where a crafted archive writes outside the intended directory. This is the highest-value class here because charts are routinely pulled from repositories nobody audits Template rendering that reaches the filesystem, the network or process execution rather than staying inside the manifest it produces Provenance and signature verification accepting a chart whose signature does not actually match, which removes the only integrity control in the chart supply chain OCI registry client defects where a redirect, a manifest or a layer an attacker controls is fetched or trusted, including digest verification that does not verify Plugin installation running code from a location the user did not intend, since plugins execute with the user's own privileges Values merging that lets a dependency chart override a parent's security-relevant settings, or that reads a file the user did not name Credential disclosure from release storage, the repository client's stored authentication or the registry credential file Anything that changes the rendered manifest in a way the operator did not ask for, because the output is applied with the operator's RBAC and nobody reads it before it lands Program rules Submit through sorona.xyz. This project runs no bounty of its own; we validate, coordinate disclosure with the maintainers, and pay you directly. Report privately to [email protected] , the address helm.sh publishes. PGP keys are available and optional, and acknowledgement comes within three business days Do not file this at the Bugcrowd programme named Helm. That programme belongs to thehelm.com, an unrelated email-appliance company, and has nothing to do with this project Do not file it at the Kubernetes HackerOne programme either. Helm is a separate GitHub organisation and that paid scope does not reach it Nothing is paid at any severity. The CNCF runs no umbrella bounty for its projects outside Kubernetes itself Say whether the finding needs a malicious chart, a malicious chart repository or a malicious registry. Those are three different trust boundaries and only some deployments cross all three State whether it reproduces through the Helm CLI, the Go SDK or both. Argo CD and Flux embed the SDK, so an SDK-reachable defect has a much wider blast radius than a CLI one Disclosure Coordinated privately with the Helm security team through the CNCF list, which acknowledges within three business days and publishes a GitHub Security Advisory with a CVE alongside a patched release. Because the SDK is embedded in GitOps controllers, the coordination reaches those consumers before publication. Hold detail until the advisory and the fixed release are out. Safe harbor Sorona will not pursue legal action against you for good-faith research submitted to us in line with this policy. We cannot speak for the upstream project, its vendor, or any third party, and we do not grant authorization on their behalf. You are responsible for understanding and following the laws that apply to you, wherever you are, and for staying within any scope the project has defined. Submit a vulnerability