TiKV bug bounty programs
tikv.org Updated
TiKV runs one public program: a Sorona bug bounty paying up to $5,000.
- Top reward
- $5,000
- Sorona
- Programs
- 1
- 1 pays cash
- Targets in scope
- 10
- 2 types
- Last change
- None yet
- Tracked since Nov 2026
Where to report
The one public program TiKV runs.
| Program | Critical | High | Medium | Low | Top reward | Safe harbor | KYC | First response | Status |
|---|---|---|---|---|---|---|---|---|---|
|
TiKV
Sorona · Bug bounty |
$5,000 | $2,500 | $1,000 | $100 | $5,000 | Partial | – | – | Open |
-
- Critical
- $5,000
- High
- $2,500
- Medium
- $1,000
- 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
10 targets. 5 excluded.
-
https://tikv.org
Web
-
Backup, restore and SST import paths, which take files from outside the cluster and load them into a region
Products and areas
-
PingCAP's guidelines apply to "PingCAP's core open-source products and publicly available internet applications, including but not limited to" its SaaS domains "as well as components directly related to the TiDB product, such as TiKV, TiDB, TiFlash, PD, etc.", so github.com/tikv/tikv is in scope by name and on the Core Business rows
Products and areas
-
The Coprocessor, which executes pushed-down query fragments inside the storage node rather than in the SQL layer above it
Products and areas
-
The distributed transactional key-value engine, the raftstore and its Raft consensus implementation, and region split, merge and scheduling
Products and areas
-
The gRPC service surface defined by kvproto, which carries the raw KV API, the transactional KV API and every message a client, a peer or the PD scheduler sends
Products and areas
-
The RocksDB-backed storage engine, including the unsafe code around the FFI boundary
Products and areas
-
The status and metrics HTTP server, the debug endpoints behind it, and the configuration reload path
Products and areas
-
TLS and mTLS between TiKV, PD and TiDB nodes, which is the only thing separating a cluster peer from anyone else on the network
Products and areas
-
Transaction handling: the Percolator-style two-phase commit, lock resolution, and MVCC garbage collection
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.
-
Anything PingCAP judges to fail its validity criteria or its reward conditions, which is discretionary by the terms of the guidelines themselves
-
Components with no direct relationship to the TiDB product, since the guidelines anchor on PingCAP's core open-source products and the components directly related to TiDB
-
Duplicate reports, where PingCAP explicitly reserves the right to decide whether any reward is issued
-
General Business assets, meaning sites and components outside the core products, which price on the lower half of the same table rather than on TiKV's Core Business rows
-
Reports sent only to [email protected], the address the repository's own SECURITY.md gives, because that is an unpaid CNCF list and the money is on [email protected]
Recent changes
Reward and scope changes across every TiKV program, newest first.
No changes recorded yet. New targets and reward moves show up here and in the RSS feed.
Recent CVEs
Published vulnerabilities in TiKV products, from the NVD.
-
CVE-2023-30636 High
TiKV 6.1.2 allows remote attackers to cause a denial of service (fatal error, with RpcStatus UNAVAILABLE for "not leader") upon an attempt to start a node in a situation where the context deadline is exceeded
-
CVE-2023-30635 High
TiKV 6.1.2 allows remote attackers to cause a denial of service (fatal error) upon an attempt to get a timestamp from the Placement Driver.
About this page
This page gathers every public program listed under tikv.org: 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.