Skip to content

Bug bounty program

Platform
HackerOne
Bounties
Pays
Assets in scope
82
Disclosed reports
77
Subdomains
662
Vendor on CyberSIXT
Kubernetes (120 CVEs, 0 exploited)

Most upvoted reports77

All reports
Most upvoted reports of Kubernetes
ReportWeaknessDisclosedBountyVotes
Node disk DOS by writing to container /etc/hostsAnalysed#867699Denial of Service2020-07-22$1,000161
Injection in path parameter of Ingress-nginxAnalysed#2701701Command and Code Injection2026-03-07–91
elections.k8s.io uses weak session secret key, may place elections at riskAnalysed#1387366Cryptography2025-09-19$25086
Bypass validation parts in AWS IAM Authenticator for KubernetesAnalysed#1580493Authentication2023-05-25$2,50068
CVE-2023-5528: Insufficient input sanitization in in-tree storage plugin leads to privilege escalation on Windows nodesAnalysed#2231019Command and Code Injection2023-12-21$5,00067
Subdomain Takeover Via via Dangling NS records on Amazon Route 53 http://api.e2e-kops-aws-canary.test-cncf-aws.canary.k8s.ioAnalysed#746000Authentication2020-11-29$25062
Ingress nginx annotation injection causes arbitrary command executionAnalysed#1728174Command and Code Injection2023-11-24$2,50057
Authenticated kubernetes principal with restricted permissions can retrieve ingress-nginx serviceaccount token and secrets across all namespacesAnalysed#1249583Access Control2021-12-04–55
Privilege Escalation in kOps using GCE/GCP ProviderAnalysed#1842829Access Control2023-08-04$2,50052
SSRF vulnerability can be exploited when a hijacked aggregated api server such as metrics-server returns 30XAnalysed#1544133Server-Side Request Forgery2022-12-10$1,00051

Subdomains662

Subdomains of Kubernetes
NameScopeFirst seen
exploding.k8s.ioNot in the scope2026-11-14
famf.k8s.ioNot in the scope2026-11-14
feature.k8s.ioNot in the scope2026-11-14
features.k8s.ioNot in the scope2026-11-14
foo.k8s.ioNot in the scope2026-11-14
gcsweb.k8s.ioNot in the scope2026-11-14
get.k8s.ioNot in the scope2026-11-14
git.k8s.iogitNot in the scope2026-11-14
go.k8s.ioNot in the scope2026-11-14
config.go.k8s.ioNot in the scope2026-11-14
goroutinecertificates.k8s.ioNot in the scope2026-11-14
gubernator.k8s.ioNot in the scope2026-11-14
hcr.k8s.ioNot in the scope2026-11-14
issue.k8s.ioNot in the scope2026-11-14
issues.k8s.ioNot in the scope2026-11-14
jenkins.k8s.iociNot in the scope2026-11-14
k8s-infra-cdn-cf-sandbox-ame.k8s.iotest, toolsNot in the scope2026-11-14
k8s-infra-prow.k8s.iotoolsNot in the scope2026-11-14
kep.k8s.ioNot in the scope2026-11-14
discovery.kops.k8s.ioNot in the scope2026-11-14
kubeadm.k8s.ioNot in the scope2026-11-14
metrics.k8s.iomonitoringNot in the scope2026-11-14
custom.metrics.k8s.iomonitoringNot in the scope2026-11-14
external.metrics.k8s.iomonitoringNot in the scope2026-11-14
migration.k8s.ioNot in the scope2026-11-14
minikube.k8s.ioNot in the scope2026-11-14
networking.k8s.ioNot in the scope2026-11-14
gateway.networking.k8s.ioNot in the scope2026-11-14
gateways.gateway.networking.k8s.ioNot in the scope2026-11-14
networkpolicy.networking.k8s.ioNot in the scope2026-11-14
new-gcsweb.k8s.ioNot in the scope2026-11-14
node.k8s.ioNot in the scope2026-11-14
node-perf-dash.k8s.iotestNot in the scope2026-11-14
node-perf-dash-staging.k8s.iostaging, testNot in the scope2026-11-14
oauth2-proxy.k8s.ioauthNot in the scope2026-11-14
packages.k8s.ioNot in the scope2026-11-14
prod-cdn.packages.k8s.ioNot in the scope2026-11-14
perf-dash.k8s.iotestNot in the scope2026-11-14
perf-dash-canary.k8s.iostaging, testNot in the scope2026-11-14
go.link.pkghash.k8s.ioNot in the scope2026-11-14
go.link.pkghashbytes.k8s.ioNot in the scope2026-11-14
pkgs.k8s.ioNot in the scope2026-11-14
pr.k8s.ioNot in the scope2026-11-14
pr-test.k8s.iotestNot in the scope2026-11-14
etcdserver.protoevents.k8s.ioNot in the scope2026-11-14
prow.k8s.ioIn scope2026-11-14
prow-canary.k8s.iostagingNot in the scope2026-11-14
monitoring.prow-canary.k8s.iomonitoring, stagingNot in the scope2026-11-14
docs.prow.k8s.ioNot in the scope2026-11-14
mimir.prow.k8s.ioNot in the scope2026-11-14
monitoring.prow.k8s.iomonitoringNot in the scope2026-11-14
monitoring-eks.prow.k8s.iomonitoringNot in the scope2026-11-14
monitoring-gke.prow.k8s.iomonitoringNot in the scope2026-11-14
prs.k8s.ioNot in the scope2026-11-14
redirect.k8s.ioNot in the scope2026-11-14
registry.k8s.iotoolsNot in the scope2026-11-14
registry-sandbox.k8s.iotest, toolsNot in the scope2026-11-14
cdn.registry.k8s.iotoolsNot in the scope2026-11-14
rel.k8s.ioNot in the scope2026-11-14
release.k8s.ioNot in the scope2026-11-14
releases.k8s.ioNot in the scope2026-11-14
relnotes.k8s.ioNot in the scope2026-11-14
reviewable.k8s.ioNot in the scope2026-11-14
sbom.k8s.ioNot in the scope2026-11-14
scheduling.k8s.ioNot in the scope2026-11-14
servicecatalog.k8s.ioNot in the scope2026-11-14
sigs.k8s.ioNot in the scope2026-11-14
agent-sandbox.sigs.k8s.iotestNot in the scope2026-11-14
capz.sigs.k8s.ioNot in the scope2026-11-14
cloud-provider-aws.sigs.k8s.ioNot in the scope2026-11-14
cloud-provider-azure.sigs.k8s.ioNot in the scope2026-11-14
cloud-provider-vsphere.sigs.k8s.ioNot in the scope2026-11-14
cluster-api.sigs.k8s.ioapiNot in the scope2026-11-14
cluster-api-aws.sigs.k8s.ioapiNot in the scope2026-11-14
cluster-api-cloudstack.sigs.k8s.ioapiNot in the scope2026-11-14
cluster-api-gcp.sigs.k8s.ioapiNot in the scope2026-11-14
cluster-api-ibmcloud.sigs.k8s.ioapiNot in the scope2026-11-14
main.cluster-api-ibmcloud.sigs.k8s.ioapiNot in the scope2026-11-14
release-0-12.cluster-api-ibmcloud.sigs.k8s.ioapiNot in the scope2026-11-14
release-0-3.cluster-api-ibmcloud.sigs.k8s.ioapiNot in the scope2026-11-14
release-0-4.cluster-api-ibmcloud.sigs.k8s.ioapiNot in the scope2026-11-14
release-0-5.cluster-api-ibmcloud.sigs.k8s.ioapiNot in the scope2026-11-14
release-0-6.cluster-api-ibmcloud.sigs.k8s.ioapiNot in the scope2026-11-14
release-0-7.cluster-api-ibmcloud.sigs.k8s.ioapiNot in the scope2026-11-14
cluster-api-openstack.sigs.k8s.ioapiNot in the scope2026-11-14
cluster-api-operator.sigs.k8s.ioapiNot in the scope2026-11-14
main.cluster-api.sigs.k8s.ioapiNot in the scope2026-11-14
master.cluster-api.sigs.k8s.ioapiNot in the scope2026-11-14
release-0-1.cluster-api.sigs.k8s.ioapiNot in the scope2026-11-14
release-0-2.cluster-api.sigs.k8s.ioapiNot in the scope2026-11-14
release-0-3.cluster-api.sigs.k8s.ioapiNot in the scope2026-11-14
release-0-4.cluster-api.sigs.k8s.ioapiNot in the scope2026-11-14
release-1-0.cluster-api.sigs.k8s.ioapiNot in the scope2026-11-14
release-1-1.cluster-api.sigs.k8s.ioapiNot in the scope2026-11-14
release-1-10.cluster-api.sigs.k8s.ioapiNot in the scope2026-11-14
release-1-11.cluster-api.sigs.k8s.ioapiNot in the scope2026-11-14
release-1-12.cluster-api.sigs.k8s.ioapiNot in the scope2026-11-14
release-1-13.cluster-api.sigs.k8s.ioapiNot in the scope2026-11-14
release-1-14.cluster-api.sigs.k8s.ioapiNot in the scope2026-11-14
release-1-2.cluster-api.sigs.k8s.ioapiNot in the scope2026-11-14

2 names are covered by the program's own scope; 0 were first seen this week. Names come from ProjectDiscovery's public Chaos dataset (passive sources: certificate logs, DNS and other public data), matched to the program by its listing and its own domain scope. A name being in a dataset is not permission to test it: only what the program's own scope says is in scope, and its policy decides. CyberSIXT does not resolve, probe or scan these names. Tags come from the name alone. Source: ProjectDiscovery Chaos. Subdomains on the Atlas, or search the subdomains of every program.

A name in a dataset is not permission to test it: the program's own scope and rules decide. Data as of 2026-11-15.