CVE-2025-64513 Milvus Proxy has Critical Authentication Bypass Vulnerability
Unauthenticated attackers can bypass authentication in Milvus Proxy to gain full administrative access, allowing them to read, modify, or delete data and manage the cluster.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2025-64513?
CVE-2025-64513 is a critical authentication bypass vulnerability in milvus-io milvus, published on 10 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Milvus is an open-source vector database built for generative AI applications. An unauthenticated attacker can exploit a vulnerability in versions prior to 2.4.24, 2.5.21, and 2.6.5 to bypass all authentication mechanisms in the Milvus Proxy component, gaining full administrative access to the Milvus cluster. This grants the attacker the ability to read, modify, or delete data, and to perform privileged administrative operations such as database or collection management. This issue has been fixed in Milvus 2.4.24, 2.5.21, and 2.6.5. If immediate upgrade is not possible, a temporary mitigation can be applied by removing the sourceID header from all incoming requests at the gateway, API gateway, or load balancer level before they reach the Milvus Proxy. This prevents attackers from exploiting the authentication bypass behavior.
Weakness: CWE-287
Which versions are affected by CVE-2025-64513?
10 open source packages ship an affected version, including github.com/milvus-io/milvus and milvus.
| Package | Affected | Fixed in |
|---|---|---|
github.com/milvus-io/milvus Go | All versions | 0.10.3-0.20251107071934-6102f001a971 |
github.com/milvus-io/milvus Go | All versions | 0.10.3-0.20251107071934-6102f001a971 |
github.com/milvus-io/milvus Go | All versions | 0.10.3-0.20251107071934-6102f001a971 |
github.com/milvus-io/milvus Go | From 0.10.4 | 2.4.24 |
github.com/milvus-io/milvus Go | From 0.10.4 | 2.4.24 |
github.com/milvus-io/milvus Go | From 2.5.0 | 2.5.21 |
4 more packages
github.com/milvus-io/milvus Go | From 2.5.0 | 2.5.21 |
github.com/milvus-io/milvus Go | From 2.6.0 | 2.6.5 |
github.com/milvus-io/milvus Go | From 2.6.0 | 2.6.5 |
milvus Bitnami | All versions | 2.4.24, 2.5.21, 2.6.5 |
How do I fix CVE-2025-64513?
Upgrade github.com/milvus-io/milvus to a fixed version for your release line: 0.10.3-0.20251107071934-6102f001a971, 2.4.24, 2.5.21 or 2.6.5.
Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.
Is CVE-2025-64513 being exploited?
There is no known exploitation of CVE-2025-64513 in the wild and no public exploit code.
Public exploit code: 2 proofs of concept on GitHub.
Sources
Also known as BIT-milvus-2025-64513, GHSA-mhjq-8c7m-3f7p, GO-2025-4114.