Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Path traversal by drive name in Windows environment#2307225 | Valid | File and Path Handling | Medium | 2025-01-27 | – | 59 |
| Path traversal by monkey-patching Buffer internals#2218653 | Valid | File and Path Handling | – | 2024-02-15 | – | 36 |
| Windows Device Names (CON, PRN, AUX) Bypass Path Traversal Protection in path.normalize()#3160912 | Valid | File and Path Handling | High | 2025-07-15 | – | 35 |
| Multiple permission model bypasses due to improper path traversal sequence sanitization#2259914 | Valid | File and Path Handling | – | 2024-02-15 | – | 20 |
| Off-by-slash vulnerability in nodejs.org and iojs.org#1631350 | Valid | File and Path Handling | – | 2022-08-24 | – | 12 |
| Filesystem experimental permissions policy does not handle path traversal cases.#1952978 | Valid | File and Path Handling | – | 2023-07-20 | – | 5 |
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.