Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Public Jenkins instance with /script enabledAnalysed#403402 | Valid | Command and Code Injection | Critical | 2018-09-10 | – | 74 |
| Remote Code Execution at http://tw.corp.ubnt.comAnalysed#269066 | Valid | Command and Code Injection | Critical | 2017-11-29 | – | 61 |
| CORS Misconfiguration leading to Private Information DisclosureAnalysed#430249 | Valid | Access Control | High | 2019-06-07 | – | 57 |
| Subdomain takeover on partners.ubnt.com due to non-used CloudFront DNS entryAnalysed#145224 | Valid | Access Control | – | 2016-11-27 | – | 57 |
| Login as root without password on EdgeSwitchXAnalysed#512958 | Valid | Authentication | Medium | 2019-03-31 | – | 56 |
| Ability to log in as any user without authentication if █████████ is emptyAnalysed#215053 | Valid | Authentication | Critical | 2017-08-08 | – | 54 |
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,699 analysed so far), which can be wrong. Data as of 2026-11-15.