Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| SSRF via User-Controlled Push proxyServer in Notifications Push RegistrationAnalysed#3623149 | Valid | Server-Side Request Forgery | Medium | 2026-09-30 | – | 48 |
| Blind SSRF Vulnerability in Appstore Release Upload FormAnalysed#2925666 | Valid | Access Control | Low | 2025-01-14 | – | 43 |
| DNS pin middleware can be tricked into DNS rebinding allowing SSRFAnalysed#2115212 | Valid | Server-Side Request Forgery | Medium | 2024-01-01 | – | 38 |
| Credential Disclosure via Unvalidated directDownloadUrl (Missing DontAddCredentialsAttribute)Analysed#3400143 | Valid | Authentication | Medium | 2026-04-13 | $250 | 37 |
| Blind SSRF in Mail AppAnalysed#1869714 | Valid | Server-Side Request Forgery | Low | 2024-01-10 | – | 37 |
| SSRF via filter bypass due to lax checking on IPsAnalysed#1702864 | Valid | Server-Side Request Forgery | Medium | 2023-02-10 | $250 | 33 |
| SSRF via potential filter bypass with too lax local domain checkingAnalysed#1608039 | Valid | Server-Side Request Forgery | Low | 2022-09-16 | $250 | 30 |
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 (3,437 analysed so far), which can be wrong. Data as of 2026-11-15.