Milvus bug bounty programs
milvus.io Updated
Milvus 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
- 12
- 2 types
- Last change
- None yet
- Tracked since Nov 2026
Where to report
The one public program Milvus runs.
| Program | Critical | High | Medium | Low | Top reward | Safe harbor | KYC | First response | Status |
|---|---|---|---|---|---|---|---|---|---|
|
Milvus
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
12 targets. 6 excluded.
-
https://milvus.io
Web
-
Index build and vector search execution, including the Knowhere engine and the parsing of vectors, index files and search parameters supplied by a caller
Products and areas
-
milvus-lite, the embedded build that runs inside a client process rather than as a server
Products and areas
-
Multi-tenancy through databases, collections and partition keys, wherever isolation is claimed
Products and areas
-
No declared scope exists. The project publishes no SECURITY.md and no policy prose, and the whole of its stated position is that private vulnerability reporting is switched on for milvus-io/milvus. Treat any security defect in the Milvus tree as a fair report
Products and areas
-
Object storage handling for segment data, including the paths and credentials Milvus builds for MinIO or S3
Products and areas
-
Role-based access control: users, roles, privilege grants and the checks meant to keep one tenant's collection out of another tenant's queries
Products and areas
-
The coordinator and node set: root, query, data and index coordinators, the query, data and index nodes, and the RPC between them
Products and areas
-
The metadata store and message queue integrations as Milvus configures and consumes them, covering etcd, Pulsar and Kafka
Products and areas
-
The metrics, health and management ports, including port 9091, and everything reachable on them without a credential
Products and areas
-
The Proxy, which every client request passes through, including its authentication and the routing behind it
Products and areas
-
The RESTful and gRPC APIs in full, covering collection, partition, index, search and administrative operations
Products and areas
No target matches. Try part of a host name, such as the company name.
Out of scope 6
Don't test these. A program can exclude a host another program covers; the program you report to decides.
-
A deployment whose operator chose never to enable authentication, where the finding is the configuration rather than a defect in Milvus
-
Findings against a long-superseded release with no path to the current one
-
Resource exhaustion from expensive queries against a large index, which is a capacity question
-
Retrieval quality, embedding accuracy and model behaviour, which are not security defects
-
Vulnerabilities in etcd, Pulsar, Kafka or MinIO themselves, unless Milvus's own use of them is what makes the issue reachable
-
Zilliz Cloud and other commercial hosted products, which are outside the open-source repository
Recent changes
Reward and scope changes across every Milvus 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 Milvus products, from the NVD.
-
CVE-2026-10814 Low
A vulnerability has been found in milvus-io milvus up to 2.6.13. This vulnerability affects unknown code of the file internal/metastore/kv/rootcoord/kv_catalog.go of the component Grantee ID Hash Handler. The manipulation leads to use of weak hash. The attack needs to be performed locally. The attack's complexity is rated as high. It is stated that the exploitability is difficult. The exploit has
-
CVE-2026-26190 Critical
Milvus is an open-source vector database built for generative AI applications. Prior to 2.5.27 and 2.6.10, Milvus exposes TCP port 9091 by default, which enables authentication bypasses. The /expr debug endpoint uses a weak, predictable default authentication token derived from etcd.rootPath (default: by-dev), enabling arbitrary expression evaluation. The full REST API (/api/v1/*) is registered on
About this page
This page gathers every public program listed under milvus.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.