Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Blind SSRF on velodrome.canary.k8s.ioAnalysed#808169 | Valid | Server-Side Request Forgery | Low | 2021-01-07 | – | 16 |
| Half-Blind SSRF found in kube/cloud-controller-manager can be upgraded to complete SSRF (fully crafted HTTP requests) in vendor managed k8s service.Analysed#776017 | Valid | Server-Side Request Forgery | High | 2020-10-30 | $5,000 | 21 |
| SSRF for kube-apiserver cloudprovider sceneAnalysed#941178 | Valid | Server-Side Request Forgery | Medium | 2021-10-07 | – | 24 |
| SSRF vulnerability can be exploited when a hijacked aggregated api server such as metrics-server returns 30XAnalysed#1544133 | Valid | Server-Side Request Forgery | Medium | 2022-12-10 | $1,000 | 51 |
Status and severity are HackerOne's. “Access stated” is what the title says; “Access needed” and techniques come from CyberSIXT's analysis of the public report, where there is one, which can be wrong. Data as of 2026-11-15.