Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Cache purge requests are not authenticated#1994585 | Informative | Input Validation and Logic | Medium | 2023-05-20 | – | 9 |
| Directory listing vulnerability is disclosing names and emails, widespread (thousands of records, publicly accessible without auth)#3509437 | N/A | Information Disclosure | Critical | 2026-01-14 | – | 10 |
| SOCKS5 no-auth accepted despite username/password-only authentication#3786077 | N/A | Authentication | Medium | 2026-06-09 | – | 10 |
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 (2,699 analysed so far), which can be wrong. Data as of 2026-11-15.