Skip to content

Bug bounty reports15,219

Publicly disclosed HackerOne reports, with the platform's own outcome and severity.

Program:Uber
Status
Severity:None
Clear
Weakness
Year
Bounty paid0
Access stated
Access needed
  • No account0
  • A user account0
  • A privileged role0
  • Admin0
  • Physical or local access0
  • Not clear from the report0
Clear filters7 of 15,219 reports
Disclosed bug bounty reports
ReportStatusWeaknessSeverityDisclosedBountyVotes
Design Issue at riders.uber.com/profile#298888InformativeInput Validation and LogicNone2017-12-28–1
lert.uber.com: Few default folders/files of AURA Framework are accessible#195205ValidInformation DisclosureNone2018-12-19–5
Google Maps API Key Leakage#1321830InformativeInformation DisclosureNone2021-09-03–8
Delay of arrears notification allows Riders to take multiple rides without paying#317388ValidInput Validation and LogicNone2018-11-13–11
Physical Access to Mobile App Allows Local Attribute Updates without Authentication#165561ValidAuthenticationNone2018-12-19–12
Session not expired When logout [partners.uber.com]#231041N/ANo weakness recordedNone2017-05-26–12
deleting payment profile during active trip puts account into arrears but active trip is temporarily “free”#216373ValidInput Validation and LogicNone2017-06-28–20

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.