Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Worker permission bypass via InternalWorker leak in diagnosticsAnalysed#2575105 | Valid | Access Control | High | 2025-01-21 | – | 42 |
| Permission Model bypass: process.report writes (and overwrites) files outside --allow-fs-write pathsAnalysed#3815767 | Valid | Access Control | Low | 2026-07-30 | – | 35 |
| Permission model improperly processes UNC pathsAnalysed#2079103 | Valid | Access Control | Low | 2024-07-15 | – | 35 |
| fs.futimes() Bypasses Read-Only Permission ModelAnalysed#3390084 | Valid | Access Control | Low | 2026-01-15 | – | 34 |
| Permission Model: --allow-fs-read/--allow-fs-write radix-tree prefix-boundary over-grantAnalysed#3761342 | Valid | Access Control | High | 2026-07-29 | – | 33 |
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,187 analysed so far), which can be wrong. Data as of 2026-11-15.