Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| TLS PSK/ALPN Callback Exceptions Bypass Error Handlers, Causing DoS and FD LeakAnalysed#3473882 | Valid | Denial of Service | Medium | 2026-02-12 | – | 81 |
| HTTP Request Smuggling via Connection: close<TAB> in Node.js llhttp parserAnalysed#3723248 | Valid | Injection and Smuggling | Medium | 2026-07-31 | – | 49 |
| Http request splittingAnalysed#409943 | Valid | Injection and Smuggling | Medium | 2020-01-15 | – | 45 |
| WASI sandbox escape via symlinkAnalysed#2084280 | Valid | Access Control | Medium | 2025-05-24 | – | 44 |
| Memory leak that enables remote Denial of Service against applications processing TLS client certificatesAnalysed#3357723 | Valid | Denial of Service | Medium | 2026-02-12 | – | 34 |
| Improper Input Validation — HTTP Response Parser Unconditionally Accepts Bare CR in Status LineAnalysed#3648681 | Valid | Injection and Smuggling | Medium | 2026-07-01 | – | 30 |
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.