Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Denial of Service by resource exhaustion in fetch() brotli decodingAnalysed#2284065 | Valid | Denial of Service | Medium | 2024-03-16 | – | 27 |
| Improper handling of wildcards in --allow-fs-read and --allow-fs-writeAnalysed#2257156 | Valid | Access Control | Medium | 2024-02-15 | – | 20 |
| HTTP Request Smuggling via Content Length ObfuscationAnalysed#2237099 | Valid | Injection and Smuggling | Medium | 2024-05-03 | – | 18 |
| Bypass network import restriction via data URLAnalysed#2092749 | Valid | Access Control | Medium | 2024-07-08 | – | 18 |
| Node.js is vulnerable to the Marvin Attack (timing variant of the Bleichenbacher attack against PKCS#1 v1.5 padding)Analysed#2269177 | Valid | Cryptography | Medium | 2024-02-15 | – | 16 |
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.