UTC
Critical

Milvus: Unauthenticated Access to Restful API on Metrics Port (9091) Leads to Critical System Compromise

CVE-2026-26190 · GHSA-7ppg-37fh-vcr6 · published 2026-02-11 · updated 2026-10-22

Severity
Critical
CVSS score
9.8
Chance of exploitation (EPSS)
38.8%
Fixed in
2.6.10
  • Exploitation Public proof of concept
  • Automatable Yes
  • Technical impact Total
  • CISA SSVC
What it is

An unauthenticated remote attacker with network access to port 9091 can: 1. Exfiltrate secrets and credentials — MinIO keys, etcd credentials, user password hashes, and all internal configuration values. 2. Manipulate all data — Create, modify, and delete collections, insert or remove data, bypassing all application-level access controls. 3. Manage user accounts — Create administrative users, reset passwords, and escalate privileges. 4. Cause denial of service — Shut down proxy services, drop databases, or corrupt metadata. 5. Write arbitrary files — Potentially achieve remote code execution by writing malicious files to the filesystem via access log configuration manipulation.

What to do

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

Block external access to port 9091 using firewall rules or network policies. If running in Docker/Kubernetes, do not expose port 9091 outside the internal network. Change the etcd.rootPath from the default value by-dev to a strong, random value (partial mitigation only — does not address the unauthenticated REST API).

Affected
PackageRegistryAffectedFixed in
github.com/milvus-io/milvusGo< 2.5.272.5.27
github.com/milvus-io/milvusGo>= 2.6.0, < 2.6.102.6.10
Also in github.com/milvus-io/milvus, github.com/milvus-io/milvus
  1. CriticalMilvus Proxy has a Critical Authentication Bypass Vulnerabilitygithub.com/milvus-io/milvus, github.com/milvus-io/milvus, github.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].