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
k8s.gcr.iotoolsIn scope2026-11-14
prow.k8s.ioIn 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.