Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Child process environment injection via prototype pollution#878181 | Informative | Command and Code Injection | – | 2020-07-04 | – | 3 |
| Hostname spoofing#678487 | Informative | No weakness recorded | – | 2020-01-10 | – | 3 |
| CRLF Injection in legacy url API (url.parse().hostname)#771596 | Informative | Injection and Smuggling | Medium | 2020-01-10 | – | 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 |
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, where there is one, which can be wrong. Data as of 2026-11-15.