Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Node.js permission model bypass via unchecked Unix Domain Socket connections (UDS)Analysed#3465156 | Valid | Server-Side Request Forgery | Medium | 2026-02-12 | – | 52 |
| HTTPS Agent TLS session reuse skips hostname verification across identity policies (incomplete fix of CVE-2026-48934)Analysed#3812439 | Valid | Other weaknesses | Medium | 2026-07-30 | – | 37 |
| Denial of Service by resource exhaustion in fetch() brotli decodingAnalysed#2284065 | Valid | Denial of Service | Medium | 2024-03-16 | – | 27 |
| HTTPS Agent PFX object-array key collision allows mTLS client identity reuse across different per-request certificatesAnalysed#3816840 | Valid | Authentication | Medium | 2026-07-29 | – | 24 |
| Usage of unsafe random function in undici for choosing boundaryAnalysed#2913312 | Valid | Cryptography | Medium | 2025-01-23 | – | 24 |
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 (3,935 analysed so far), which can be wrong. Data as of 2026-11-15.