Skip to content

Bug bounty reports15,219

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

Program:Node.js
Status
Severity:High
Clear
Weakness:Denial of Service
Clear
Year
Bounty paid1
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 filters7 of 15,219 reports
Disclosed bug bounty reports
ReportStatusWeaknessSeverityDisclosedBountyVotes
"Assertion failed" in node::http2::Http2Session::~Http2Session() leads to HTTP/2 server crashAnalysed#2319584ValidDenial of ServiceHigh2024-04-08–65
Incomplete Fix for CVE-2026-21637: OCSPRequest and resumeSession Events Crash Node.js TLS Server via Unhandled Synchronous Exceptions#3781015InformativeDenial of ServiceHigh2026-06-12–41
Denial of Service via `__proto__` header name in `req.headersDistinct` (Uncaught `TypeError` crashes Node.js process)#3560402ValidDenial of ServiceHigh2026-03-30–22
http: Reading unprocessed HTTP request with unbounded chunk extension allows DoS attacks#2233486ValidDenial of ServiceHigh2024-02-15–13
HTTP/2 retained header blocks evade maxSessionMemory and enable remote memory exhaustion#3846922ValidDenial of ServiceHigh2026-08-28–12
Multiple HTTP/2 DOS Issues#589739ValidDenial of ServiceHigh2019-08-16–9
DNS Max Responses for DOS#1033107ValidDenial of ServiceHigh2020-12-16$2502

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.