# CVE-2026-26190: Milvus Allows Unauthenticated Access to Restful API on Metrics Port (9091) Leads to Critical System Compromise

> Unauthenticated access to Milvus metrics port allows arbitrary code execution and data manipulation via exposed REST APIs and debug endpoints.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Feb 2026
- **Updated:** 26 Feb 2026
- **Also known as:** BIT-milvus-2026-26190, GHSA-7ppg-37fh-vcr6, GO-2026-4481

## What is CVE-2026-26190?

CVE-2026-26190 is a critical authentication bypass vulnerability in milvus-io milvus, published on 13 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Milvus is an open-source vector database built for generative AI applications. Prior to 2.5.27 and 2.6.10, Milvus exposes TCP port 9091 by default, which enables authentication bypasses. The /expr debug endpoint uses a weak, predictable default authentication token derived from etcd.rootPath (default: by-dev), enabling arbitrary expression evaluation. The full REST API (/api/v1/*) is registered on the metrics/management port without any authentication, allowing unauthenticated access to all business operations including data manipulation and credential management. This vulnerability is fixed in 2.5.27 and 2.6.10.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-26190?

6 open source packages ship an affected version, including github.com/milvus-io/milvus and milvus. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/milvus-io/milvus` | Go | All versions | None |
| `github.com/milvus-io/milvus` | Go | All versions | 2.5.27 |
| `github.com/milvus-io/milvus` | Go | All versions | 2.5.27 |
| `github.com/milvus-io/milvus` | Go | From 2.6.0 | 2.6.10 |
| `github.com/milvus-io/milvus` | Go | From 2.6.0 | 2.6.10 |
| `milvus` | Bitnami | All versions | 2.5.27, 2.6.10 |

Products: Milvus Milvus.

## How do I fix CVE-2026-26190?

Upgrade github.com/milvus-io/milvus to a fixed version for your release line: 2.5.27 or 2.6.10.

## Is CVE-2026-26190 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-26190 exists.

Public exploit code:

- Milvus 认证安全检测脚本：CVE-2025-64513 (sourceid后门) / CVE-2026-26190 (/expr弱token) / 内部端口53100 (github_poc): https://github.com/qianlijaingshan/milvus-auth-audit
- Milvus - Unauthenticated Metrics API Access (nuclei): http/cves/2026/CVE-2026-26190.yaml

## Other vulnerabilities in milvus-io milvus

- [CVE-2026-10814](https://insights.sbomify.com/CVE-2026-10814/): milvus-io milvus Grantee ID Hash kv_catalog.go weak hash (low 2.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-26190 and fix it if it is affected.

What it is: CVE-2026-26190 is a critical authentication bypass vulnerability in milvus-io milvus, published on 13 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-26190 exists.

Affected packages and fixed versions:
- github.com/milvus-io/milvus (Go): affected all versions; no fix listed
- github.com/milvus-io/milvus (Go): affected all versions; fixed in 2.5.27
- github.com/milvus-io/milvus (Go): affected all versions; fixed in 2.5.27
- github.com/milvus-io/milvus (Go): affected from 2.6.0; fixed in 2.6.10
- github.com/milvus-io/milvus (Go): affected from 2.6.0; fixed in 2.6.10
- milvus (Bitnami): affected all versions; fixed in 2.5.27, 2.6.10

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-26190/ (Markdown: https://insights.sbomify.com/CVE-2026-26190/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-26190
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-26190
- OSV: https://osv.dev/vulnerability/CVE-2026-26190

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-26190/
Summaries are generated and may contain mistakes; the official description above is the record.