Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| PIN bypass in PassCodeActivity via back buttonAnalysed#3625210 | Valid | Authentication | Medium | 2026-06-07 | $150 | 101 |
| Private circle can be added to another circle via API despite visibility restrictionAnalysed#3511998 | Valid | Insecure Direct Object Reference | Low | 2026-05-08 | $150 | 87 |
| WebAuthn app was updated based on public keyAnalysed#3360354 | Valid | Insecure Direct Object Reference | Low | 2026-02-06 | – | 84 |
| SQL Injection in Column Type Parameter Allows Arbitrary SQL ExecutionAnalysed#3462991 | Valid | SQL Injection | High | 2026-05-15 | – | 80 |
| Stored XSS Vulnerability via SVG FileAnalysed#3357808 | Valid | Cross-site Scripting | Medium | 2025-12-05 | $150 | 79 |
| CSRF protection on OIDC login is brokenAnalysed#1878381 | Valid | Cross-Site Request Forgery | Medium | 2023-04-04 | $500 | 77 |
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 (1,199 analysed so far), which can be wrong. Data as of 2026-11-14.