Skip to content

Cloudflare bug bounty programs

cloudflare.com Updated

Cloudflare runs 6 public programs on Sorona, HackerOne and its own site; 5 pay cash, the most up to $10,000 (Cloudflare Public Bug Bounty). It also owns cfssl.org, which runs one more program.

Top reward
$10,000
HackerOne
Programs
7
6 pay cash
Targets in scope
104
4 types, deduplicated
Last change
12 Nov 2026
13 hours ago

Where to report

6 programs Cloudflare runs itself, side by side. Report where the affected target is in scope; when two programs cover it, pick the one that pays more.

Start here

CloudFlare

Self-hosted · The company-wide program. Use it when no owned company's program fits.

Amounts are the top reward per severity in the currency each program pays. Green marks the highest per severity. First response is the platform's measured average when it publishes one, else what the policy promises.

Companies Cloudflare owns

1 company with 1 program of its own. Each has its own scope and rules: report to the one that owns the asset.

What is in scope

104 targets across all 7 programs, each listed once with the programs that cover it. 70 excluded.

  • *.cloudflare.com

    Wildcards Critical

    Covered by HackerOne

  • *.cloudflarepartners.com

    Wildcards Critical

    Covered by HackerOne

  • *.teams.cloudflare.com

    Wildcards Critical

    Covered by HackerOne

  • api.cloudflare.com

    Web Critical

    Covered by HackerOne

  • cloudflareworkers.com

    Web Critical

    Covered by HackerOne

  • dash.cloudflare.com

    Web Critical

    Covered by HackerOne

  • http://github.com/cloudflare

    Web Critical

    Covered by HackerOne

  • https://cfssl.org

    Web

    Covered by cfssl

  • https://developers.cloudflare.com/agents

    Web

    Covered by Cloudflare Agents SDK

  • https://developers.cloudflare.com/cloudflare-one/connections/connect-networks

    Web

    Covered by cloudflared

  • https://developers.cloudflare.com/workers/wrangler

    Web

    Covered by Wrangler

  • https://workers.cloudflare.com

    Web

    Covered by workerd

  • one.dash.cloudflare.com

    Web Critical

    Covered by HackerOne

  • https://github.com/cloudflare/vinext

    Source code Critical

    Covered by HackerOne

  • https://github.com/cloudflare/workerd

    Source code Critical

    Covered by HackerOne

  • 1.1.1.1 Resolver

    Products and areas Critical

    Covered by HackerOne

  • AI Gateway

    Products and areas Critical

    Covered by HackerOne

  • AMP Real URL

    Products and areas Critical

    Covered by HackerOne

  • API Shield

    Products and areas Critical

    Covered by HackerOne

  • Area 1

    Products and areas Critical

    Covered by HackerOne

  • Auto-update and binary-integrity paths, where a downgrade or substituted binary turns into persistent access

    Products and areas

    Covered by cloudflared

  • Bot Management

    Products and areas Critical

    Covered by HackerOne

  • Browser Isolation

    Products and areas Critical

    Covered by HackerOne

  • Bundling of untrusted project source through the esbuild integration, and everything the build step runs on the developer's machine

    Products and areas

    Covered by Wrangler

  • CDNJS

    Products and areas Critical

    Covered by HackerOne

No target matches. Try part of a host name, such as the company name.

Out of scope 70

Don't test these. A program can exclude a host another program covers; the program you report to decides.

  • *.plugins.realtime.cloudflare.com

    HackerOne

  • api.staging.realtime.cloudflare.com

    HackerOne

  • app.dyte.io

    HackerOne

  • community.cloudflare.com

    HackerOne

  • demo.realtime.cloudflare.com

    HackerOne

  • events.www.cloudflare.com

    HackerOne

  • examples.realtime.cloudflare.com

    HackerOne

  • files.plugins.realtime.cloudflare.com

    HackerOne

  • https://php-rce.cloudflare.app

    HackerOne

  • https://playground.ai.cloudflare.com

    HackerOne

  • https://vibecoder.cloudflare.dev

    HackerOne

  • react-examples.realtime.cloudflare.com

    HackerOne

  • support.cloudflare.com

    HackerOne

  • support.cloudflarewarp.com

    HackerOne

  • test.realtime.cloudflare.com

    HackerOne

  • waf.cumulusfire.net

    HackerOne

  • https://github.com/cloudflare/agentic-inbox

    HackerOne

  • https://github.com/cloudflare/boringtun

    HackerOne

  • https://github.com/cloudflare/cf

    HackerOne

  • https://github.com/cloudflare/cloudflare-os

    HackerOne

  • https://github.com/cloudflare/computer

    HackerOne

  • https://github.com/cloudflare/moq-rs

    HackerOne

  • https://github.com/cloudflare/pp-browser-extension

    HackerOne

  • https://github.com/cloudflare/privacy-gateway-server-go

    HackerOne

  • https://github.com/cloudflare/realtimekit-web-examples

    HackerOne

  • https://github.com/cloudflare/recapn

    HackerOne

  • https://github.com/cloudflare/saffron.git

    HackerOne

  • https://github.com/cloudflare/security-audit-skill

    HackerOne

  • https://github.com/cloudflare/templates

    HackerOne

  • https://github.com/cloudflare/vibesdk

    HackerOne

  • https://github.com/cloudflare/vinext-private

    HackerOne

  • 172.65.0.0/16

    HackerOne

  • Archived, demo-only and experimental repositories under the Cloudflare org, which the policy treats as Informational

    Wrangler

  • Attacks that need local root on the connector host, which the program treats as already-lost ground

    cloudflared

  • Billing and plan-enforcement issues, which the policy caps at Low severity and a $250 maximum payout

    workerd

  • Credential findings validated by actually signing in with the credential, which the program's secret-handling rules forbid

    cloudflared

  • Customer-configured Workers and customer content on Cloudflare's edge, which belong to the customer rather than to Cloudflare and are not the researcher's to test

    Cloudflare Agents SDK

  • Demo, example and test code carried inside the repository

    cfssl

  • Denial of service against Cloudflare

    Wrangler

  • Denial of service against Cloudflare's edge

    cloudflared

  • Denial of service against Cloudflare, social engineering, and physical attacks

    Cloudflare Agents SDK

  • Duplicates of findings Cloudflare's internal AI-assisted scanning has already produced

    cfssl

  • Findings against forks or third-party tunnel wrappers rather than the upstream connector

    cloudflared

  • Findings submitted without a working proof of concept, which are ineligible at any severity

    cfssl

  • Findings that require a maintainer to approve a GitHub Actions workflow before they trigger

    workerd

  • Hardening or standards-conformance issues without a demonstrated security impact

    cfssl

  • Hardening-only findings with no demonstrated crossing of a security boundary

    Cloudflare Agents SDK

  • Issues requiring a consumer application to misuse the library in an obviously unsafe way

    Wrangler

  • Issues that were already publicly known at the time of the report

    Cloudflare Agents SDK

  • Local-only wrangler dev reproductions with no demonstrated production reachability

    workerd

  • Misconfigured user ingress rules that expose an origin exactly as the operator configured them to

    cloudflared

  • Pure API incompatibilities, standards deviations, or missing hardening in open source projects without demonstrated security impact

    Wrangler

  • Reports only affecting self-hosted or local deployments where Cloudflare production or documented production usage is not impacted

    Wrangler

  • Reports that do not clearly identify the affected asset, security boundary, attacker prerequisites, reproduction steps, and meaningful impact

    Cloudflare Agents SDK

  • Reports with no working proof of concept, which are not bounty-eligible at any severity

    workerd

  • Self-hosted-only impact with no Cloudflare production nexus or documented production usage

    cfssl

  • Severity cap to plan around: the open-source row tops out at $3,500 for a Critical, and the Tier 1 band reaching $10,000 covers production Cloudflare infrastructure as discretionary uplift

    Wrangler

  • Severity cap to plan around: the open-source row tops out at $3,500 for a Critical, since the $10,000 headline belongs to Tier 1 production Cloudflare infrastructure

    Cloudflare Agents SDK

  • Severity cap to plan around: the org-wide open-source row tops out at $3,500 for a Critical, since Cloudflare's $10,000 row is bound to production infrastructure rather than the GitHub org

    cfssl

  • Severity cap to plan around: the Tier 2 open-source row tops out at $3,500 for a Critical, since Cloudflare's $10,000 row is bound to production infrastructure rather than the GitHub org

    cloudflared

  • Source-code-only analysis with no runnable reproduction, which is closed Informational regardless of how the severity reads on paper

    Wrangler

  • Source-code-only analysis, which the policy rules out however the code reads

    cfssl

  • Testing anyone else's tunnel: stand up your own connector and your own origin, since other tenants are off limits

    cloudflared

  • The repositories Cloudflare marks explicitly ineligible for bounty: cloudflare/vinext-private, moq-rs, privacy-gateway-server-go, saffron, realtimekit-web-examples and recapn

    Cloudflare Agents SDK

  • The repositories Cloudflare marks explicitly not eligible for bounty: cloudflare/vinext-private, moq-rs, privacy-gateway-server-go, saffron and recapn

    workerd

  • The workerd runtime itself, which is its own separately named scope asset and is reported against that scope rather than this one

    Wrangler

  • The workerd runtime underneath, which the program lists as its own scope asset on a higher reward row and which belongs in a separate report

    Cloudflare Agents SDK

  • Third-party Go dependency CVEs without a demonstrated reachable path through cloudflared itself

    cloudflared

  • Turnstile

    HackerOne

  • V8 itself, which is Chrome VRP territory and already sits on the sorona.xyz paid rail as its own program

    workerd

Recent changes

Reward and scope changes across every Cloudflare program, newest first.

All changes · RSS feed

Recent CVEs

Published vulnerabilities in Cloudflare products, from the NVD.

Search NVD
  • Summary Cloudflare quiche's HTTP/3 layer was discovered to be vulnerable to resource exhaustion (i.e., memory) by means of specially crafted HTTP/3 frames. Impact HTTP/3 defines multiple frame types to support HTTP message exchanges and connection management. Each frame has a length and a payload whose length depends on the frame type. quiche was found to be vulnerable when parsing some frame type

  • Summary Cloudflare quiche's HTTP/3 layer was discovered to be vulnerable to resource exhaustion (i.e., memory) by means of specially crafted HTTP/3 frames. Impact HTTP/3 defines multiple frame types to support HTTP message exchanges and connection management. Each frame has a length and a payload whose length depends on the frame type. quiche was found to be vulnerable when parsing some frame type

  • Summary Cloudflare quiche's HTTP/3 layer was discovered to be vulnerable to resource exhaustion (i.e., memory) by means of specially crafted HTTP/3 frames. Impact HTTP/3 defines multiple frame types to support HTTP message exchanges and connection management. Each frame has a length and a payload whose length depends on the frame type. quiche was found to be vulnerable when parsing some frame type

  • Summary Cloudflare quiche's HTTP/3 layer was discovered to be vulnerable to resource exhaustion (i.e., memory) by means of specially crafted HTTP/3 frames. Impact HTTP/3 defines multiple frame types to support HTTP message exchanges and connection management. Each frame has a length and a payload whose length depends on the frame type. quiche was found to be vulnerable when parsing some frame type

  • Summary Cloudflare quiche's HTTP/3 layer was discovered to be vulnerable to resource exhaustion (i.e., memory) by means of specially crafted HTTP/3 frames. Impact HTTP/3 defines multiple frame types to support HTTP message exchanges and connection management. Each frame has a length and a payload whose length depends on the frame type. quiche was found to be vulnerable when parsing some frame type

  • Summary Cloudflare quiche's HTTP/3 layer was discovered to be vulnerable to resource exhaustion (i.e., memory) by means of specially crafted HTTP/3 frames. Impact HTTP/3 defines multiple frame types to support HTTP message exchanges and connection management. Each frame has a length and a payload whose length depends on the frame type. quiche was found to be vulnerable when parsing some frame type

  • CVE-2026-2835 Critical

    An HTTP Request Smuggling vulnerability (CWE-444) has been found in Pingora's parsing of HTTP/1.0 and Transfer-Encoding requests. The issue occurs due to improperly allowing HTTP/1.0 request bodies to be close-delimited and incorrect handling of multiple Transfer-Encoding values, allowing attackers to send HTTP/1.0 requests in a way that would desync Pingora’s request framing from backend servers’

  • CVE-2026-2833 Critical

    An HTTP request smuggling vulnerability (CWE-444) was found in Pingora's handling of HTTP/1.1 connection upgrades. The issue occurs when a Pingora proxy reads a request containing an Upgrade header, causing the proxy to pass through the rest of the bytes on the connection to a backend before the backend has accepted the upgrade. An attacker can thus directly forward a malicious payload after a req

About this page

This page gathers every public program listed under cloudflare.com and the companies Cloudflare owns: platform programs, self-hosted policies and security.txt contacts. Each program's own policy decides what is in scope and what it pays; check it before you test. Ownership comes from settled, public acquisitions, or from a program's own text naming Cloudflare.

Something wrong or missing? Report a correction.