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
Year
Bounty paid0
Access stated
  • No account0
  • A user account0
  • Admin or privileged0
Access needed
  • No account0
  • A user account0
  • A privileged role0
  • Admin0
  • Physical or local access0
  • Not clear from the report0
Clear filters23 of 15,219 reports
Disclosed bug bounty reports
ReportStatusWeaknessSeverityDisclosedBountyVotes
HTTP/2 retained header blocks evade maxSessionMemory and enable remote memory exhaustion#3846922ValidDenial of ServiceHigh2026-08-28–12
Node.js WebCrypto AES Integer Overflow Leads to Remote Process Abort (DoS)#3760016ValidMemory CorruptionHigh2026-06-25–13
Node --run POSIX positional argument escaping allows shell command injection#3817602InformativeCommand and Code InjectionHigh2026-06-23–13
Re-entrant `nghttp2_session_mem_send()` during `nghttp2_session_mem_recv()` causes heap-use-after-free in Node.js HTTP/2#3833629ValidMemory CorruptionHigh2026-08-28–17
Node.js unicode dot separator handling can lead to tls wildcard-depth authentication bypass due to resolver and verifier hostname normalization mismat#3688064ValidInjection and SmugglingHigh2026-06-25–18
dns.resolve truncates names containing NUL char#4038342ValidAccess ControlHigh2026-10-23–18
Bypass incomplete fix of CVE-2024-27980#2461831ValidCommand and Code InjectionHigh2024-07-09–20
Denial of Service via `__proto__` header name in `req.headersDistinct` (Uncaught `TypeError` crashes Node.js process)#3560402ValidDenial of ServiceHigh2026-03-30–22
Missing AES-GCM Authentication Tag Validation and Improper Deprecation Handling#3463949InformativeCryptographyHigh2025-12-19–24
TLS certificate hostname bypass when the host loosely resolves to an IP address#4006744ValidCryptographyHigh2026-10-23–24
TLS certificate hostname bypass when the IP is written fullwidth digits#4038287ValidCryptographyHigh2026-10-23–29
Memory Corruption via TOCTOU Race in SharedArrayBuffer UTF-8 Decode (`StringBytes::Encode`)#3752489InformativeRace ConditionsHigh2026-05-23–32
Permission Model: --allow-fs-read/--allow-fs-write radix-tree prefix-boundary over-grant#3761342ValidAccess ControlHigh2026-07-29–33
FS Permissions Bypass#3417819ValidMisconfiguration and Insecure DesignHigh2026-02-12–34
Windows Device Names (CON, PRN, AUX) Bypass Path Traversal Protection in path.normalize()#3160912ValidFile and Path HandlingHigh2025-07-15–35
Improper error handling in async cryptographic operations crashes process#2817648ValidCryptographyHigh2025-05-14–37
Windows Device Names Still Allow Path Traversal in UNC Paths After CVE-2025-27210 Fix#3255707InformativeFile and Path HandlingHigh2025-07-28–39
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
Worker permission bypass via InternalWorker leak in diagnostics#2575105ValidAccess ControlHigh2025-01-21–42
Timeout-based race conditions make Uint8Array/Buffer.alloc non-zerofilled#3405778ValidMemory CorruptionHigh2026-02-12–43
NULL pointer dereference in node:sqlite DatabaseSync#applyChangeset() via malformed SQLite changeset#3736889InformativeMemory CorruptionHigh2026-05-23–44
HashDoS in V8#3131758ValidCryptographyHigh2025-07-15–53
Incomplete fix for CVE-2026-21637: loadSNI() in _tls_wrap.js lacks try/catch leading to Remote DoS#3556769ValidNo weakness recordedHigh2026-04-23–59

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

Updated AboutDevelopersSign in