Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Crashes/Buffer at 0x2C0086,name=PBrowser::Msg_Destroy#281682 | Informative | Memory Corruption | Medium | 2017-10-24 | – | – |
| Enforce minimum master password complexity#280282 | N/A | Authentication | Medium | 2017-10-19 | – | 1 |
| Email Spoofing Possible on torproject.org Email Domain#423336 | N/A | Input Validation and Logic | Medium | 2018-10-16 | – | 3 |
| Multiple Path Transversal Vulnerabilites#273377 | N/A | File and Path Handling | Medium | 2023-11-28 | – | 11 |
| SQL Injection in parameter REPORT#269347 | Informative | SQL Injection | Medium | 2023-11-28 | – | 23 |
| Conflux-queued zero-length RELAY_END triggers heap out-of-bounds readAnalysed#3709605 | Valid | Memory Corruption | Medium | 2026-09-10 | – | 33 |
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 (2,942 analysed so far), which can be wrong. Data as of 2026-11-15.