Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| [Variation of #1554049] 1-Click Chaining of Self-XSS, Cookie Tossing and AntiCSRF Token Prediction leads to auto approval in Access Temp AuthAnalysed#3321406 | Valid | No weakness recorded | High | 2026-04-14 | – | 39 |
| HTTP Request Smuggling via Unsanitized Hop-by-Hop HeadersAnalysed#3622877 | Valid | Access Control | High | 2026-09-14 | $1,500 | 54 |
| AI Playground XSS to steal user-chat messages and access to connected MCP ServerAnalysed#3424998 | Valid | Cross-site Scripting | Low | 2026-02-26 | – | 62 |
| [Variation of #3321406] YetAnother 1-Click Chaining of Self-XSS, Cookie Tossing and AntiCSRF Token Prediction leads to auto approval in AccessTempAuthAnalysed#3423950 | Valid | Cross-site Scripting | High | 2026-04-14 | – | 63 |
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.