Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Information Disclosure of Garbage Collection CycleAnalysed#981796 | Valid | Information Disclosure | Low | 2020-11-04 | – | 33 |
| Information Disclosure of Garbage Collection Cycle 'Again'Analysed#1026196 | Valid | Information Disclosure | Low | 2020-12-16 | $100 | 41 |
| Bypass of image rewriting / tracking blocker via srcsetAnalysed#1021885 | Valid | Information Disclosure | Medium | 2020-12-03 | $1,000 | 56 |
| Subdomain Takeover due to ████████ NS records at us-east4.37signals.comAnalysed#1342422 | Valid | Information Disclosure | Medium | 2021-09-17 | – | 77 |
| AWS keys and user cookie leakage via uninitialized memory leak in outdated librsvg version in BasecampAnalysed#2107680 | Valid | Information Disclosure | High | 2023-09-21 | $8,868 | 248 |
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 (3,187 analysed so far), which can be wrong. Data as of 2026-11-15.