Skip to content
Connect AISign inSign up free

Bug bounty program

KU

Kubernetes

Open on HackerOneAtlas
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

Root
Scope
Name suggests
First seen
Text file662 names
Subdomains of Kubernetes
NameScopeFirst seen
v1-9.docs.kubernetes.ioNot in the scope2026-11-14
www.v1-9.docs.kubernetes.ioNot in the scope2026-11-14
downloadconfig.kubernetes.ioNot in the scope2026-11-14
endpointslice.kubernetes.ioNot in the scope2026-11-14
examples.kubernetes.ioNot in the scope2026-11-14
feature.kubernetes.ioNot in the scope2026-11-14
features.kubernetes.ioNot in the scope2026-11-14
gcr.kubernetes.ioNot in the scope2026-11-14
asia.gcr.kubernetes.ioNot in the scope2026-11-14
eu.gcr.kubernetes.ioNot in the scope2026-11-14
us.gcr.kubernetes.ioNot in the scope2026-11-14
gcsweb.kubernetes.ioNot in the scope2026-11-14
get.kubernetes.ioNot in the scope2026-11-14
git.kubernetes.iogitNot in the scope2026-11-14
go.kubernetes.ioNot in the scope2026-11-14
gubernator.kubernetes.ioNot in the scope2026-11-14
hello.kubernetes.ioNot in the scope2026-11-14
alb.ingress.kubernetes.ioNot in the scope2026-11-14
nginx.ingress.kubernetes.ioNot in the scope2026-11-14
validate.nginx.ingress.kubernetes.ioNot in the scope2026-11-14
nnginx.ingress.kubernetes.ioNot in the scope2026-11-14
u003enginx.ingress.kubernetes.ioNot in the scope2026-11-14
issue.kubernetes.ioNot in the scope2026-11-14
issues.kubernetes.ioNot in the scope2026-11-14
kep.kubernetes.ioNot in the scope2026-11-14
kubectl.kubernetes.ioNot in the scope2026-11-14
n0kubectl.kubernetes.ioNot in the scope2026-11-14
naddonmanager.kubernetes.ioNot in the scope2026-11-14
napp.kubernetes.ioNot in the scope2026-11-14
nbeta.kubernetes.ioNot in the scope2026-11-14
netlify-move.kubernetes.ioNot in the scope2026-11-14
nnode.kubernetes.ioNot in the scope2026-11-14
node.kubernetes.ioNot in the scope2026-11-14
node-role.kubernetes.ioNot in the scope2026-11-14
packages.kubernetes.ioNot in the scope2026-11-14
pkgs.kubernetes.ioNot in the scope2026-11-14
pr.kubernetes.ioNot in the scope2026-11-14
pr-test.kubernetes.iotestNot in the scope2026-11-14
prow.kubernetes.ioNot in the scope2026-11-14
prs.kubernetes.ioNot in the scope2026-11-14
pv.kubernetes.ioNot in the scope2026-11-14
rel.kubernetes.ioNot in the scope2026-11-14
releases.kubernetes.ioNot in the scope2026-11-14
reviewable.kubernetes.ioNot in the scope2026-11-14
rnode-role.kubernetes.ioNot in the scope2026-11-14
sbom.kubernetes.ioNot in the scope2026-11-14
sigs.kubernetes.ioNot in the scope2026-11-14
slack.kubernetes.ioNot in the scope2026-11-14
slack-infra.kubernetes.ioNot in the scope2026-11-14
get-an-invite-at.slack.kubernetes.ioNot in the scope2026-11-14
spartakus.kubernetes.ioNot in the scope2026-11-14
storageclass.kubernetes.ioNot in the scope2026-11-14
submit-queue.kubernetes.ioNot in the scope2026-11-14
testgrid.kubernetes.ioNot in the scope2026-11-14
u003eapp.kubernetes.ioNot in the scope2026-11-14
u003enode.kubernetes.ioNot in the scope2026-11-14
u003enode-role.kubernetes.ioNot in the scope2026-11-14
velodrome.kubernetes.ioNot in the scope2026-11-14
www.kubernetes.ioNot in the scope2026-11-14
youtube.kubernetes.ioNot in the scope2026-11-14
yt.kubernetes.ioNot in the scope2026-11-14
yum.kubernetes.ioNot 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.

CyberSIXTSignal over noise
Sign inSign up free

Updated