Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| View-only guests could see deleted Collectives pages in the trashbinAnalysed#3521434 | Valid | Access Control | Low | 2026-05-08 | – | 87 |
| Read-only users can restore old versionsAnalysed#1356508 | Valid | Access Control | Medium | 2024-06-14 | $500 | 38 |
| files_lock: a write-share collaborator can place a TYPE_TOKEN lock that permanently denies the file owner, survives share revocation and account deletAnalysed#3770482 | Valid | Access Control | Medium | 2026-09-18 | – | 31 |
| Non-admin users can reset app allowlist to the defaultAnalysed#2250398 | Valid | Input Validation and Logic | Medium | 2024-01-18 | – | 28 |
| Improper handling of request URLs in nextcloud/guests allows guest users to bypass app allowlistAnalysed#2251074 | Valid | Injection and Smuggling | Medium | 2024-01-18 | – | 22 |
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 (4,182 analysed so far), which can be wrong. Data as of 2026-11-15.