Skip to content

Bug bounty reports15,219

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

Program:Monero
Status
Severity
Weakness
Year
Bounty paid0
Access stated
  • No account0
  • A user account0
  • Admin or privileged0
Access needed:No account
  • No account2
  • A user account0
  • A privileged role0
  • Admin0
  • Physical or local access0
  • Not clear from the report0
Technique
Clear filters2 of 15,219 reports
Disclosed bug bounty reports
ReportStatusWeaknessSeverityDisclosedBountyVotes
low-level p2p ping + tcp flooding leads to a remote crash in monerodAnalysed#2858802ValidNo weakness recordedCritical2025-04-14–97
Critical Deadlock Vulnerability in Monero RPC Leading to Complete Node ParalysisAnalysed#3307874ValidDenial of ServiceCritical2026-05-06–97

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