Prow bug bounty programs
k8s.io Updated
Prow runs three public programs: a Sorona bug bounty paying up to $10,000, a Sorona bug bounty paying up to $3,125 and a Sorona bug bounty paying up to $3,125.
- Top reward
- $10,000
- Sorona
- Programs
- 3
- 3 pay cash
- Targets in scope
- 24
- 2 types, deduplicated
- Last change
- None yet
- Tracked since Nov 2026
Where to report
3 programs, side by side. Report where the affected target is in scope; when two programs cover it, pick the one that pays more.
Start here
Prow
Sorona · Pays the most of the 3 programs: up to $10,000.
| Program | Critical | High | Medium | Low | Top reward | Safe harbor | KYC | First response | Status |
|---|---|---|---|---|---|---|---|---|---|
|
Prow
Sorona · Bug bounty |
$10k (highest) | $1,250 | $250 | $100 | $10,000 | Partial | – | 24 hours promised | Open |
|
Minikube
Sorona · Bug bounty |
– | $3,125 (highest) | $625 (highest) | $125 (highest) | $3,125 | Partial | – | 24 hours promised | Open |
|
kOps
Sorona · Bug bounty |
– | $3,125 | $625 | $125 | $3,125 | Partial | – | 24 hours promised | Open |
-
- Critical
- $10k (highest)
- High
- $1,250
- Medium
- $250
- Low
- $100
- Safe harbor
- Partial
- First response
- 24 hours promised
-
- Critical
- –
- High
- $3,125 (highest)
- Medium
- $625 (highest)
- Low
- $125 (highest)
- Safe harbor
- Partial
- First response
- 24 hours promised
-
- Critical
- –
- High
- $3,125
- Medium
- $625
- Low
- $125
- Safe harbor
- Partial
- First response
- 24 hours promised
Amounts are the top reward per severity in the currency each program pays. Green marks the highest per severity. First response is the platform's measured average when it publishes one, else what the policy promises.
What is in scope
24 targets across all 3 programs, each listed once with the programs that cover it. 18 excluded.
-
Certificate, credential and kubeconfig handling on the developer's workstation
Products and areas
Covered by Minikube
-
Configuration and credential handling: config.yaml and plugins.yaml loading, the ProwJob resource, GitHub token brokering through ghproxy, and the secrets a build cluster holds
Products and areas
Covered by Prow
-
Host-to-guest networking: port forwarding, minikube tunnel and minikube mount, which push cluster services onto the workstation's network and host directories into the cluster
Products and areas
Covered by Minikube
-
Node bootstrap: nodeup, kops-controller and the bootstrap token and node-authorizer path that decides what a joining machine is allowed to claim to be
Products and areas
Covered by kOps
-
The addon system and the manifests it applies, including how Minikube stands up the Kubernetes Dashboard, registry, ingress and metrics-server
Products and areas
Covered by Minikube
-
The cluster lifecycle commands and everything behind them: create, update, rolling-update and delete, along with the cluster spec API and the validation applied to it
Products and areas
Covered by kOps
-
The command handlers a contributor can reach: /test, /retest, /ok-to-test, /lgtm, /approve and the OWNERS resolution underneath them
Products and areas
Covered by Prow
-
The driver layer across Docker, Podman, KVM2, HyperKit, VirtualBox, QEMU and the rest, including how each one isolates the guest it creates from the host
Products and areas
Covered by Minikube
-
The in-cluster components kOps ships and manages, including protokube, dns-controller, channels and the addon manifests they apply
Products and areas
Covered by kOps
-
The ISO, the kicbase container image and the preload tarballs, along with the download and verification path that pulls Kubernetes binaries and images onto the workstation
Products and areas
Covered by Minikube
-
The job lifecycle, meaning plank, sinker, crier, horologium and the pod utilities (clonerefs, initupload, entrypoint, sidecar) that check out and run untrusted pull-request code in the build cluster
Products and areas
Covered by Prow
-
The kOps CLI itself, including kubeconfig export and the credentials it writes on the operator's workstation
Products and areas
Covered by kOps
-
The kubernetes/kops repository, which the program lists as a bounty-eligible source-code asset up to critical severity under the instruction "Kubernetes Operations (kops) - Production Grade K8s Installation, Upgrades, and Management", priced at Tier 2: $100 at Low rising to $5,000 at Critical
Products and areas
Covered by kOps
-
The kubernetes/minikube repository, which the program lists as a bounty-eligible source-code asset up to critical severity under the instruction "Run Kubernetes locally", priced at Tier 2: $100 at Low rising to $5,000 at Critical
Products and areas
Covered by Minikube
-
The minikube binary and its whole command surface: start, stop, delete, tunnel, mount, service, dashboard, ssh, cp, image and addons
Products and areas
Covered by Minikube
-
The rest of kubernetes/test-infra, since the whole repository is the asset: the CI configuration for the Kubernetes project along with the release and artifact-publishing tooling it carries
Products and areas
Covered by Prow
-
The state store, meaning the S3 or GCS bucket layout, the cluster spec kept there and the secrets and certificates alongside it, plus every path that reads or writes any of that
Products and areas
Covered by kOps
-
The webhook ingress hook and the plugin set behind it, including the trust model that decides whose comment Prow will act on
Products and areas
Covered by Prow
-
tide, which decides what actually merges into kubernetes/kubernetes, and deck, the web UI that serves job logs and artifacts at prow.k8s.io
Products and areas
Covered by Prow
-
Two assets, both bounty-eligible up to critical severity: the kubernetes/test-infra repository, listed as "Test infrastructure for the Kubernetes project", and prow.k8s.io as a live URL asset carrying the instruction "Please limit automated scanning to 1qps". Prow prices as Tier 3 infrastructure, $100 to $2,500, promoted to Tier 1 and $10,000 where the compromise reaches code or artifact modification
Products and areas
Covered by Prow
-
What kOps generates for the cloud account, covering IAM policies, instance profiles and security groups, and what it lays down in the cluster, covering control plane flags, etcd topology and certificate material
Products and areas
Covered by kOps
No target matches. Try part of a host name, such as the company name.
Out of scope 18
Don't test these. A program can exclude a host another program covers; the program you report to decides.
-
Automated scanning of prow.k8s.io above the stated 1 qps limit, which the program asks you not to run
Prow
-
Broken link hijacking in documentation
Prow
-
Clusters built by releases outside the three most recent supported ones
kOps
-
Code in kubernetes-sigs/prow, since the paid asset for this project is kubernetes/test-infra
Prow
-
Community management tooling: mailing lists, Slack, calendars and similar
Prow
-
Config and path disclosure without demonstrated credential leakage, which the program does not usually treat as a vulnerability
Prow
-
Container escapes to the host "unless the attack path traverses a Kubernetes process (e.g. kubelet)", which the program states explicitly
Minikube
-
Deprecated components, which are not supported targets
kOps
-
Deprecated drivers and deprecated components, which are not supported targets
Minikube
-
Findings that require an insecure configuration, per "Attacks relying on insecure configurations (subject to the Security Response Committee's opinion)"
kOps
-
Kubernetes running on Windows or other non-Linux operating systems
kOps
-
Non-Kubernetes binaries distributed as cluster addons, which belong to their own upstream projects
Minikube
-
Non-Linux Kubernetes targets, which trims part of the macOS and Windows driver surface
Minikube
-
Releases older than the three most recent, which fall outside the supported window
Minikube
-
Reports from a maintainer, or from the author or reviewer of the vulnerable code, which the program cannot award
Prow kOps
-
Reports from maintainers, or from the author or reviewer of the vulnerable code, which cannot be awarded
Minikube
-
Social engineering against maintainers
Prow
-
Vendor-specific cloud provider plugins, meaning the AWS, GCE, Azure, OpenStack and vSphere shims, which the scope table marks eligible_for_bounty: false
kOps
Recent changes
Reward and scope changes across every Prow program, newest first.
No changes recorded yet. New targets and reward moves show up here and in the RSS feed.
About this page
This page gathers every public program listed under k8s.io: 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.