# CVE-2025-64513: milvus Auth Bypass — Fixed in 2.4.24 🐹 Go Not in CISA KEV # CVE-2025-64513 — milvus [Fix: milvus-io/milvus#45379](https://github.com/milvus-io/milvus/pull/45379) CVE-2025-64513 is a Improper Authentication vulnerability in github.com/milvus-io/milvus. A fix is available for github.com/milvus-io/milvus — see the affected versions and patch details below. Milvus Proxy has Critical Authentication Bypass Vulnerability Also known asBIT-milvus-2025-64513[GHSA-mhjq-8c7m-3f7p](/vulnerability/GHSA-mhjq-8c7m-3f7p)GO-2025-4114 Published Nov 10, 2025 Updated Oct 28, 2026 Affected 4 pkgs Patched 4 / 4 Exploits None indexed Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS) ## Exploitation Status ### No confirmed exploitation observed yet - CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks. - A successful exploit gives an attacker total control of the affected component, not partial access. - CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment. Exploitation and automatability from CISA’s SSVC triage for CVE-2025-64513. ## EPSS Exploitation Probability [via FIRST.org ↗](https://www.first.org/epss/) 0.9%probability of exploitation in next 30 days Lower Risk0.00% Lower risk than most CVEs59th percentile — riskier than 59% of all scored CVEsHighest risk 0.00%0.52%1.05%1.57%0.2%0.9%May 26Sep 26Nov 26 Probability of exploitation in the next 30 days, from [FIRST.org EPSS](https://www.first.org/epss/). ## Real-World Exposure 4 pkgs affected 🐹`github.com/milvus-io/milvus`🐹`github.com/milvus-io/milvus`🐹`github.com/milvus-io/milvus`🐹`github.com/milvus-io/milvus` Real-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 #### 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](https://github.com/milvus-io/milvus/pull/45391) • [Fix for 2.5 branch](https://github.com/milvus-io/milvus/pull/45383) • [Fix for 2.6 branch](https://github.com/milvus-io/milvus/pull/45379) Special thanks to the Volcengine Milvus team at ByteDance([liumingzhe.5689@bytedance.com](mailto:liumingzhe.5689@bytedance.com)) for responsibly discovering, reporting, and coordinating the disclosure of this critical authentication bypass vulnerability with the Milvus maintainers. ## Affected Packages 4 total 4 fixed Ecosystem Package Vulnerable range Fix 🐹Go `github.com/milvus-io/milvus` ≥ 0.10.4&&< 2.4.24 2.4.24`go get github.com/milvus-io/milvus@v2.4.24` 🐹Go `github.com/milvus-io/milvus` ≥ 2.5.0&&< 2.5.21 2.5.21`go get github.com/milvus-io/milvus@v2.5.21` 🐹Go `github.com/milvus-io/milvus` ≥ 2.6.0&&< 2.6.5 2.6.5`go get github.com/milvus-io/milvus@v2.6.5` 🐹Go `github.com/milvus-io/milvus` all versions 0.10.3-0.20251107071934-6102f001a971`go get github.com/milvus-io/milvus@v0.10.3-0.20251107071934-6102f001a971` ## Detection & mitigation playbook Open-source dependency 1. ### Detect Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/milvus-io/milvus, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version. 2. ### 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. 3. ### Workarounds Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used. ## Frequently Asked Questions \### 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 O3 Security · Impact-Aware SCA ### Is CVE-2025-64513 in your dependencies? Find it across Go, including transitive dependencies. [Scan my dependencies](/book-demo) [How O3 SCA works](/impact-aware-sca)