Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Improper HTTP header block termination in llhttpAnalysed#2054283 | Valid | Injection and Smuggling | Medium | 2025-06-13 | – | 122 |
| Path traversal by drive name in Windows environmentAnalysed#2307225 | Valid | File and Path Handling | Medium | 2025-01-27 | – | 59 |
| Assertion error in node_url.cc via malformed URL format leads to Node.js crashAnalysed#3546390 | Valid | Denial of Service | Medium | 2026-03-26 | – | 40 |
| Uncatchable "Maximum call stack size exceeded" error on Node.js via async_hooks leads to process crashes bypassing error handlersAnalysed#3456295 | Valid | Input Validation and Logic | Medium | 2026-02-12 | – | 35 |
| HTTP/2 sessions never clean up after GOAWAY on invalid protocol errorsAnalysed#3658225 | Valid | Denial of Service | Medium | 2026-06-18 | – | 33 |
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.