Skip to content

Bug bounty reports15,219

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

Program:Node.js
Status
Severity
Weakness:Authentication
Clear
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 filters2 of 15,219 reports
Disclosed bug bounty reports
ReportStatusWeaknessSeverityDisclosedBountyVotes
HTTPS Agent PFX object-array key collision allows mTLS client identity reuse across different per-request certificates#3816840ValidAuthenticationMedium2026-07-29–24
Proxy-Authorization header not cleared on cross-origin redirect in undici.request#2408074ValidAuthenticationLow2024-05-03–9

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

Updated AboutDevelopersSign in