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 |
| Critically Sensitive Spring Boot Endpoints ExposedAnalysed#1022048 | Valid | Access Control | Critical | 2022-02-10 | – | 59 |
| 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 |
| subdomain takeover at news-static.semrush.comAnalysed#294201 | Valid | Access Control | High | 2018-01-10 | – | 40 |
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,187 analysed so far), which can be wrong. Data as of 2026-11-15.