Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Hostname spoofing#678487 | Informative | No weakness recorded | – | 2020-01-10 | – | 3 |
| Insecure loading of ICU data through ICU_DATA environment variable#1625036 | Valid | No weakness recorded | – | 2023-03-19 | – | 4 |
| Unbounded decompression chain in HTTP responses on Node.js Fetch API via Content-Encoding leads to resource exhaustion#3456148 | Valid | No weakness recorded | – | 2026-02-23 | – | 25 |
| CWE-195 in ExternalMemoryAccounter::Increase()#3302484 | Informative | No weakness recorded | – | 2025-08-26 | – | 55 |
| Incomplete fix for CVE-2026-21637: loadSNI() in _tls_wrap.js lacks try/catch leading to Remote DoS#3556769 | Valid | No weakness recorded | High | 2026-04-23 | – | 59 |
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 (348 analysed so far), which can be wrong. Data as of 2026-11-14.