CoreDNS bug bounty programs
coredns.io Updated
CoreDNS runs one public program: a Sorona bug bounty paying up to $1,500.
- Top reward
- $1,500
- Sorona
- Programs
- 1
- 1 pays cash
- Targets in scope
- 8
- 2 types
- Last change
- None yet
- Tracked since Nov 2026
Where to report
The one public program CoreDNS runs.
| Program | Critical | High | Medium | Low | Top reward | Safe harbor | KYC | First response | Status |
|---|---|---|---|---|---|---|---|---|---|
|
CoreDNS
Sorona · Bug bounty |
– | – | – | $100 | $1,500 | Partial | – | – | Open |
-
- Critical
- –
- High
- –
- Medium
- –
- Low
- $100
- Safe harbor
- Partial
Amounts are the top reward per severity in the currency each program pays. First response is the platform's measured average when it publishes one, else what the policy promises.
What is in scope
8 targets. 5 excluded.
-
https://coredns.io
Web
-
Caching and forwarding behaviour end to end, covering which answer from which source is served to which client
Products and areas
-
Every server transport the daemon speaks, including the DoH, DoT and gRPC listeners
Products and areas
-
The Corefile parser and the plugin ordering it produces, which decides what runs before what on every query
Products and areas
-
The DNS server core and the miekg/dns layer it is built on, where every query and every upstream answer is decoded
Products and areas
-
The kubernetes plugin in full: it reads live Service and Endpoint state, and it is the place where a namespace boundary is expressed as a DNS boundary and can therefore be crossed
Products and areas
-
The project takes security reports at [email protected] and through GitHub private advisory reporting, and draws no boundary narrower than the main CoreDNS repository itself
Products and areas
-
The whole bundled plugin chain rather than the handful of plugins that happen to carry a CVE, forward, cache, rewrite and template among them
Products and areas
No target matches. Try part of a host name, such as the company name.
Out of scope 5
Don't test these. A program can exclude a host another program covers; the program you report to decides.
-
Cluster misconfiguration such as an over-permissive kubernetes plugin zone, which is an operator decision
-
DNS amplification treated as an operational property of the protocol rather than as a defect in CoreDNS
-
Kubernetes itself and other CNCF components, which are different projects and are not covered by this program
-
One-line patches that fix non-exploitable crashes, including crashes that only amount to resource exhaustion, which the Patch Rewards rules say will not generally be rewarded
-
Third-party plugins that are not in the main CoreDNS repository
Recent changes
Reward and scope changes across every CoreDNS program, newest first.
No changes recorded yet. New targets and reward moves show up here and in the RSS feed.
About this page
This page gathers every public program listed under coredns.io: 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.
Something wrong or missing? Report a correction.