Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Bypass of Cloudflare's Cache Keys and WAF via header overflow#3027461 | Valid | Access Control | High | 2025-11-18 | – | 77 |
| Hijack all emails sent to any domain that uses Cloudflare Email ForwardingAnalysed#1419341 | Valid | Access Control | Critical | 2022-07-28 | $6,000 | 76 |
| HTTP Request Smuggling via Unsanitized Hop-by-Hop HeadersAnalysed#3622877 | Valid | Access Control | High | 2026-09-14 | $1,500 | 54 |
| Enable 2Fa verification without verifying emailAnalysed#1618021 | Valid | Access Control | Medium | 2022-08-31 | – | 40 |
| A malicious actor could rotate tokens of a victim, given that he knows the victim's token IDAnalysed#1525309 | Valid | Access Control | High | 2023-04-13 | – | 34 |
| Privilege escalation to root in Pages build image v2#1979372 | Valid | Access Control | Low | 2023-05-26 | $350 | 10 |
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,182 analysed so far), which can be wrong. Data as of 2026-11-15.