Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Cloudflare CASB Confused Deputy ProblemAnalysed#1952124 | Valid | No weakness recorded | Critical | 2023-06-07 | $3,300 | 97 |
| Hijack all emails sent to any domain that uses Cloudflare Email ForwardingAnalysed#1419341 | Valid | Access Control | Critical | 2022-07-28 | $6,000 | 76 |
| `use-mcp`'s oauth2 process uses a window.open call with untrusted mcp server provided data allowing for code execution under the page using itAnalysed#3211031 | Valid | Cross-site Scripting | Medium | 2025-09-30 | $550 | 75 |
| Yet Another CASB Integration Takeover of Active IntegrationsAnalysed#2094346 | Valid | No weakness recorded | High | 2023-11-13 | – | 68 |
| [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 |
| Blind SSRF on platform.dash.cloudflare.com Due to Sentry misconfigurationAnalysed#1467044 | Valid | Server-Side Request Forgery | Low | 2022-08-31 | – | 54 |
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 (1,932 analysed so far), which can be wrong. Data as of 2026-11-15.