UTC
Critical

Milvus Proxy has a Critical Authentication Bypass Vulnerability

CVE-2025-64513 · GHSA-mhjq-8c7m-3f7p · published 2025-11-13

Severity
Critical
CVSS score
9.3
Chance of exploitation (EPSS)
0.87%
Fixed in
2.6.5
  • Exploitation No known exploitation
  • Automatable Yes
  • Technical impact Total
  • CISA SSVC
What it is

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.

What to do

Upgrade github.com/milvus-io/milvus to 2.6.5 or later.

Has the problem been patched? What versions should users upgrade to? This issue has been fixed in the following versions: Users should upgrade to these patched versions or later to mitigate the vulnerability.

If you cannot upgrade yet

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.

Affected
PackageRegistryAffectedFixed in
github.com/milvus-io/milvusGo< 0.10.3-0.20251107071934-6102f001a9710.10.3-0.20251107071934-6102f001a971
github.com/milvus-io/milvusGo>= 0.10.4, < 2.4.242.4.24
github.com/milvus-io/milvusGo>= 2.5.0, < 2.5.212.5.21
github.com/milvus-io/milvusGo>= 2.6.0, < 2.6.52.6.5
Also in github.com/milvus-io/milvus, github.com/milvus-io/milvus, github.com/milvus-io/milvus, github.com/milvus-io/milvus
  1. CriticalMilvus: Unauthenticated Access to Restful API on Metrics Port (9091) Leads to Critical System Compromisegithub.com/milvus-io/milvus, github.com/milvus-io/milvus
  2. Lowmilvus: RBAC grantee-id uses truncated MD5 (64-bit), enabling privilege-binding collisions and cross-role privilege forgerygithub.com/milvus-io/milvus

The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].