CVE-2025-64513
CVE-2025-64513 is a Improper Authentication vulnerability in github.com/milvus-io/milvus. O3 Security confirms whether CVE-2025-64513 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Milvus Proxy has Critical Authentication Bypass Vulnerability
Blast Radius
github.com/milvus-io/milvus🐹github.com/milvus-io/milvus🐹github.com/milvus-io/milvus🐹github.com/milvus-io/milvusReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/milvus-io/milvus | ≥ 0.10.4&&< 2.4.24 | 2.4.24 |
| 🐹Go | github.com/milvus-io/milvus | ≥ 2.5.0&&< 2.5.21 | 2.5.21 |
| 🐹Go | github.com/milvus-io/milvus | ≥ 2.6.0&&< 2.6.5 | 2.6.5 |
| 🐹Go | github.com/milvus-io/milvus | all versions | 0.10.3-0.20251107071934-6102f001a971 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/milvus-io/milvus. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/milvus-io/milvus to 2.4.24 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-64513 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2025-64513 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2025-64513. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2025-64513 in your dependencies?
O3 detects CVE-2025-64513 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.