Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Malformed HTTP/2 SETTINGS frame leads to reachable assert#800140 | Valid | Denial of Service | Critical | 2020-07-03 | $250 | 14 |
| Denial of Service by resource exhaustion CWE-400 due to unfinished HTTP/1.1 requests#868834 | Valid | Denial of Service | Critical | 2020-10-17 | $250 | 8 |
| Slowloris, body parsing#799072 | Valid | Denial of Service | Low | 2020-10-17 | $250 | 8 |
| Fix for CVE-2018-12122 can be bypassed via keep-alive requests#453513 | Valid | Denial of Service | Medium | 2020-02-13 | – | 3 |
| DNS Max Responses for DOS#1033107 | Valid | Denial of Service | High | 2020-12-16 | $250 | 2 |
| Node.js HTTP/2 Large Settings Frame DoS#446662 | Valid | Denial of Service | Low | 2020-07-02 | – | 2 |
| Http response is not ended although underlying socket is already destroyed#676710 | Informative | Denial of Service | – | 2020-01-15 | – | 1 |
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,935 analysed so far), which can be wrong. Data as of 2026-11-15.