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 |
| SSRF via potential filter bypass with too lax local domain checkingAnalysed#1608039 | Valid | Server-Side Request Forgery | Low | 2022-09-16 | $250 | 30 |
| SSRF protection bypassAnalysed#736867 | Valid | Server-Side Request Forgery | Medium | 2020-03-14 | $100 | 18 |
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.