Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| CSRF-Token leak by request forgery#221432 | Valid | Cross-Site Request Forgery | – | 2017-10-09 | – | 6 |
| CSRF Token Bypass in Account Deletion#182487 | Valid | Cross-Site Request Forgery | – | 2017-04-20 | – | 7 |
| Drive-by arbitrary file deletion in the GDK via letter_opener_web gem#1353103 | Valid | Cross-Site Request Forgery | – | 2021-11-12 | $750 | 27 |
| [Admin Panel] CSRF to resume/pause runner#415238 | Valid | Cross-Site Request Forgery | – | 2020-12-01 | – | 60 |
| CSRF on /api/graphql allows executing mutations through GET requests#1122408 | Valid | Cross-Site Request Forgery | – | 2021-08-02 | $3,370 | 88 |
| Account takeover due to insufficient URL validation on RelayState parameter#1923672 | Valid | Cross-Site Request Forgery | – | 2023-05-30 | $2,450 | 99 |
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 (227 analysed so far), which can be wrong. Data as of 2026-11-14.