Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Github information leakedAnalysed#676212 | Valid | Information Disclosure | High | 2019-09-25 | – | 344 |
| OAuth `redirect_uri` bypass using IDN homograph attack resulting in user's access token leakageAnalysed#861940 | Valid | Information Disclosure | Medium | 2020-06-18 | – | 265 |
| Exposure of service tokens to webpack bundleAnalysed#1717210 | Valid | Information Disclosure | High | 2024-03-08 | – | 56 |
| API key (api.semrush.com) leak in JS-fileAnalysed#1218754 | Valid | Information Disclosure | Medium | 2022-09-05 | – | 55 |
| php info file and sql backup at vendor's subdomain#1358249 | Valid | Information Disclosure | Low | 2021-12-08 | – | 14 |
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.