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 in writeFile via Unsafe Prefix Containment Check Allows Out-of-Directory WritesAnalysed#3634571 | Valid | File and Path Handling | Medium | 2026-03-31 | – | 21 |
| Authorization header leak in ssrf_filter via cross-host redirect leads to credential theft and unauthorized accessAnalysed#3642600 | Valid | No weakness recorded | – | 2026-04-15 | – | 42 |
| Arbitrary File WriteAnalysed#3384150 | Valid | File and Path Handling | High | 2025-10-19 | – | 56 |
| SSRF Filter Bypass via Unblocked NAT64 Local-Use IPv6 Prefix (64:ff9b:1::/48)Analysed#3634400 | Valid | Server-Side Request Forgery | High | 2026-03-31 | – | 65 |
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 (4,365 analysed so far), which can be wrong. Data as of 2026-11-15.