Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| WASI sandbox escape via symlinkAnalysed#2084280 | Valid | Access Control | Medium | 2025-05-24 | – | 44 |
| Timeout-based race conditions make Uint8Array/Buffer.alloc non-zerofilledAnalysed#3405778 | Valid | Memory Corruption | High | 2026-02-12 | – | 43 |
| fs.futimes() Bypasses Read-Only Permission ModelAnalysed#3390084 | Valid | Access Control | Low | 2026-01-15 | – | 34 |
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,182 analysed so far), which can be wrong. Data as of 2026-11-15.