Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| deleting payment profile during active trip puts account into arrears but active trip is temporarily “free”#216373 | Valid | Input Validation and Logic | None | 2017-06-28 | – | 20 |
| Session not expired When logout [partners.uber.com]#231041 | N/A | No weakness recorded | None | 2017-05-26 | – | 12 |
| Physical Access to Mobile App Allows Local Attribute Updates without Authentication#165561 | Valid | Authentication | None | 2018-12-19 | – | 12 |
| Delay of arrears notification allows Riders to take multiple rides without paying#317388 | Valid | Input Validation and Logic | None | 2018-11-13 | – | 11 |
| Google Maps API Key Leakage#1321830 | Informative | Information Disclosure | None | 2021-09-03 | – | 8 |
| lert.uber.com: Few default folders/files of AURA Framework are accessible#195205 | Valid | Information Disclosure | None | 2018-12-19 | – | 5 |
| Design Issue at riders.uber.com/profile#298888 | Informative | Input Validation and Logic | None | 2017-12-28 | – | 1 |
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,437 analysed so far), which can be wrong. Data as of 2026-11-15.