Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Node.js HTTP/2 Large Settings Frame DoS#446662 | Valid | Denial of Service | – | 2020-07-02 | – | 2 |
| Use After Free in crypto.randomFill#340053 | Informative | Memory Corruption | – | 2020-01-15 | – | 2 |
| Http response is not ended although underlying socket is already destroyed#676710 | Informative | Denial of Service | – | 2020-01-15 | – | 1 |
| Vulnerability in http-parser & embedded NULL header handling#536954 | Valid | Memory Corruption | – | 2020-02-13 | – | 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 (227 analysed so far), which can be wrong. Data as of 2026-11-14.