Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| loader.js is not secure#629879 | N/A | Command and Code Injection | – | 2020-06-11 | – | 3 |
| Unexpected input validation of octal literals in nodejs v15.12.0 and below returns defined values for all undefined octal literals.#1141623 | N/A | Memory Corruption | – | 2021-06-14 | – | 4 |
| Your page has 2 blocking CSS resources. This causes a delay in rendering your page.#365968 | N/A | Memory Corruption | – | 2018-07-15 | – | 8 |
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 (549 analysed so far), which can be wrong. Data as of 2026-11-14.