Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Complete Admin account takeover due to PhpDebugBar turned on in Uber's production serverAnalysed#1883806 | Valid | Misconfiguration and Insecure Design | Medium | 2023-08-23 | – | 90 |
| Avoiding Surge PricingAnalysed#125250 | Valid | Misconfiguration and Insecure Design | – | 2016-08-11 | – | 45 |
| Stealing users password (Limited Scenario)Analysed#163067 | Valid | Misconfiguration and Insecure Design | – | 2016-09-29 | – | 35 |
| Possibility to brute force invite codes in riders.uber.comAnalysed#125505 | Valid | Misconfiguration and Insecure Design | – | 2016-06-13 | $5,000 | 35 |
| Brute-Forcing invite codes in partners.uber.com#144616 | Valid | Misconfiguration and Insecure Design | – | 2016-07-26 | $750 | 4 |
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, where there is one, which can be wrong. Data as of 2026-11-15.