Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Lack or Origin check leads to Cross-Site Websocket Hijacking (CSWSH)Analysed#535436 | Valid | Access Control | High | 2020-01-04 | $800 | 134 |
| `socket` command allows sending data over WebSockets to arbitrary origins from Grammarly ExtensionAnalysed#395729 | Valid | No weakness recorded | High | 2019-07-15 | – | 140 |
| Ability to DOS any organization's SSO and open up the door to account takeoversAnalysed#976603 | Valid | Authentication | High | 2021-04-15 | $10,500 | 260 |
| Account takeover through the combination of cookie manipulation and XSSAnalysed#534450 | Valid | Cross-site Scripting | High | 2019-12-03 | – | 292 |
| Employee's GitHub Token Found In Travis CI Build LogsAnalysed#496937 | Valid | Information Disclosure | High | 2019-05-22 | $5,000 | 408 |
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.