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:A user account
Technique
Clear filters9 of 15,219 reports
Disclosed bug bounty reports
ReportStatusWeaknessSeverityDisclosedBountyVotes
HashDoS in V8Analysed#3131758ValidCryptographyHigh2025-07-15–53
Worker permission bypass via InternalWorker leak in diagnosticsAnalysed#2575105ValidAccess ControlHigh2025-01-21–42
Path traversal by monkey-patching Buffer internalsAnalysed#2218653ValidFile and Path HandlingHigh2024-02-15–36
FS Permissions BypassAnalysed#3417819ValidMisconfiguration and Insecure DesignHigh2026-02-12–34
Permission Model: --allow-fs-read/--allow-fs-write radix-tree prefix-boundary over-grantAnalysed#3761342ValidAccess ControlHigh2026-07-29–33
setuid() does not drop all privileges due to io_uringAnalysed#2170226ValidAccess ControlHigh2024-03-16–24
Multiple permission model bypasses due to improper path traversal sequence sanitizationAnalysed#2259914ValidFile and Path HandlingHigh2024-02-15–20
dns.resolve truncates names containing NUL charAnalysed#4038342ValidAccess ControlHigh2026-10-23–18
DNS rebinding in --inspect (insufficient fix of CVE-2022-32212 affecting macOS devices)Analysed#1632921ValidAccess ControlHigh2022-09-28–16

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.