Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Program | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|---|
| RC Between GitHub's Repo Update REST API and updateTeamsRepository GraphQL Mutation Results in Covert and Persistent Admin Access RetentionAnalysed#2357443 | Valid | GitHub | Misconfiguration and Insecure Design | Medium | 2024-09-17 | – | 50 |
| [h1-2102] shopApps query from the graphql at /users/api returns all existing created apps, including private onesAnalysed#1085332 | Valid | Shopify | Information Disclosure | Medium | 2022-07-15 | $1,900 | 35 |
| SSRF in notifications.server configurationAnalysed#850114 | Valid | Phabricator | Server-Side Request Forgery | Medium | 2020-05-15 | $300 | 28 |
| Stored XSS on apps.shopify.comAnalysed#1107726 | Valid | Shopify | Cross-site Scripting | Medium | 2021-04-08 | – | 26 |
| Access to private file's of helpdesk.Analysed#804534 | Valid | Lark Technologies | Access Control | Medium | 2022-10-18 | – | 21 |
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,614 analysed so far), which can be wrong. Data as of 2026-11-15.