Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Proxy credentials leaked in ERR_PROXY_TUNNEL error message#3720313 | Valid | Information Disclosure | Medium | 2026-06-25 | – | 4 |
| Unbounded memory growth in `node:http2` clients via attacker-controlled ORIGIN frames#3676863 | Valid | Denial of Service | Medium | 2026-06-25 | – | 4 |
| Embedded-nul hostnames can lead to silent authority rebinding due to c-string truncation in resolver bindings#3656716 | Valid | Access Control | Medium | 2026-06-25 | – | 4 |
| Permission Model bypass via FileHandle.utimes() in the promises API#3625987 | Valid | Access Control | Low | 2026-06-25 | – | 4 |
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, where there is one, which can be wrong. Data as of 2026-11-15.