CVE-2025-64513: Milvus Proxy has Critical Authentication Bypass Vulnerability
Impact What kind of vulnerability is it? Who is impacted? An unauthenticated attacker can exploit this vulnerability 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. All users running affected Milvus versions are strongly advised to upgrade immediately.
Patches Has the problem been patched? What versions should users upgrade to? This issue has been fixed in the following versions: • Milvus 2.4.24 • Milvus 2.5.21 • Milvus 2.6.5
Users should upgrade to these patched versions or later to mitigate the vulnerability.
Workarounds Is there a way for users to fix or remediate the vulnerability without upgrading? 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.
References Are there any links users can visit to find out more?
The following pull requests contain the fixes for the affected Milvus branches: • Fix for 2.4 branch • Fix for 2.5 branch • Fix for 2.6 branch
Special thanks to the Volcengine Milvus team at ByteDance(liumingzhe.5689@bytedance.com) for responsibly discovering, reporting, and coordinating the disclosure of this critical authentication bypass vulnerability with the Milvus maintainers.
Other sources
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.
— NVD
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-64513?
CVE-2025-64513 is a critical vulnerability due to its potential for unauthenticated access to Milvus Proxy, allowing full administrative control.
How do I fix CVE-2025-64513?
To mitigate CVE-2025-64513, update Milvus Proxy to version 2.4.24, 2.5.21, or 2.6.5 or later.
What impacts does CVE-2025-64513 have on Milvus Proxy?
CVE-2025-64513 allows unauthenticated attackers to bypass all authentication mechanisms in Milvus Proxy.
Which versions of Milvus Proxy are affected by CVE-2025-64513?
CVE-2025-64513 affects Milvus Proxy versions prior to 2.4.24, 2.5.21, and 2.6.5.
Is an authenticated user safe from CVE-2025-64513?
An authenticated user is not safe from CVE-2025-64513, as the vulnerability allows an unauthenticated attacker to gain administrative access.