Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Bypass incomplete fix of CVE-2024-27980#2461831 | Valid | Command and Code Injection | High | 2024-07-09 | – | 20 |
| Node --run POSIX positional argument escaping allows shell command injection#3817602 | Informative | Command and Code Injection | High | 2026-06-23 | – | 13 |
| Pull Request #12949 - Security Implications without CVE assignment#415329 | Valid | Command and Code Injection | – | 2020-02-13 | – | 5 |
| DNS rebinding in --inspect via invalid octal IP address#1710652 | Valid | Command and Code Injection | – | 2022-12-07 | – | 4 |
| Child process environment injection via prototype pollution#878181 | Informative | Command and Code Injection | – | 2020-07-04 | – | 3 |
| loader.js is not secure#629879 | N/A | Command and Code Injection | – | 2020-06-11 | – | 3 |
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 (227 analysed so far), which can be wrong. Data as of 2026-11-14.