Skip to content

Bug bounty reports15,219

Publicly disclosed HackerOne reports, with the platform's own outcome and severity.

Program:Node.js
Status
Severity:Medium
Clear
Weakness:Denial of Service
Clear
Year
Bounty paid0
Access stated
  • No account0
  • A user account0
  • Admin or privileged0
Access needed
  • No account1
  • A user account0
  • A privileged role0
  • Admin0
  • Physical or local access0
  • Not clear from the report0
Technique
Clear filters11 of 15,219 reports
Disclosed bug bounty reports
ReportStatusWeaknessSeverityDisclosedBountyVotes
TLS PSK/ALPN Callback Exceptions Bypass Error Handlers, Causing DoS and FD LeakAnalysed#3473882ValidDenial of ServiceMedium2026-02-12–81
Assertion error in node_url.cc via malformed URL format leads to Node.js crash#3546390ValidDenial of ServiceMedium2026-03-26–40
Memory leak that enables remote Denial of Service against applications processing TLS client certificates#3357723ValidDenial of ServiceMedium2026-02-12–34
HTTP/2 sessions never clean up after GOAWAY on invalid protocol errors#3658225ValidDenial of ServiceMedium2026-06-18–33
Denial of Service by resource exhaustion in fetch() brotli decoding#2284065ValidDenial of ServiceMedium2024-03-16–27
GOAWAY HTTP/2 frames cause memory leak outside heap#2841362ValidDenial of ServiceMedium2025-02-06–13
Reachable assertion in node:zlib sync API crashes the entire process via spoofed TypedArray byteLength (all 11 *Sync functions affected)#3857258ValidDenial of ServiceMedium2026-08-28–12
dns.resolveAny() Aborts the Node.js Process When a DNS Response Contains More Than 256 A Records#3795657ValidDenial of ServiceMedium2026-08-28–12
Memory leak in Node.js HTTP/2 server via WINDOW_UPDATE on stream 0 leads to resource exhaustion#3531737ValidDenial of ServiceMedium2026-03-30–7
Unbounded memory growth in `node:http2` clients via attacker-controlled ORIGIN frames#3676863ValidDenial of ServiceMedium2026-06-25–4
Fix for CVE-2018-12122 can be bypassed via keep-alive requests#453513ValidDenial of ServiceMedium2020-02-13–3

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 (1,683 analysed so far), which can be wrong. Data as of 2026-11-15.