LiveActive security incident?Get immediate response
CVE Record

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

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.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

Milvus versions before 2.5.27 and 2.6.10 can expose powerful management and REST functions without authentication on port 9091. An unauthenticated network user could manipulate data, manage credentials, and compromise confidentiality, integrity, and availability. This is critical for any internet-exposed or broadly reachable Milvus deployment.

Executive priority

Prioritize within the next emergency patch cycle for any reachable Milvus deployment. This affects AI/vector database infrastructure and can enable unauthenticated data manipulation and credential management. Internet-exposed systems should be treated as urgent.

Technical view

CVE-2026-26190 is a CWE-306 missing-authentication flaw in Milvus. The metrics/management port 9091 exposes /api/v1/* without authentication, and the /expr debug endpoint uses a predictable default token derived from etcd.rootPath. Affected versions are <2.5.27 and >=2.6.0,<2.6.10. CVSS is 9.8.

Likely exposure

Exposure is likely where Milvus port 9091 is reachable from untrusted networks, shared internal networks, or application environments. Default exposure is noted in the advisory description. Risk is lower if the port is strictly isolated and only trusted administrative components can reach it.

Exploitation context

No CISA KEV listing or cited source in the bundle confirms active exploitation. However, the issue is network-accessible, requires no credentials, and affects sensitive business operations. Treat reachable vulnerable instances as high-priority because abuse could directly affect data and credentials.

Researcher notes

The strongest source is the GitHub security advisory, supported by release tags and a fixing commit. Evidence identifies affected version ranges and fixed versions. Public sources provided do not establish exploitation in the wild. Avoid assuming impact beyond Milvus deployments matching the listed versions and exposure conditions.

Mitigation direction

  • Upgrade Milvus to 2.5.27 or 2.6.10, depending on your release branch.
  • Restrict network access to port 9091 to trusted administrative paths only.
  • Review vendor advisory and release notes before deploying updates.
  • Audit exposed Milvus services for unintended management-port reachability.
  • Rotate credentials if unauthorized access to vulnerable port 9091 is suspected.

Validation and detection

  • Inventory Milvus deployments and record exact versions.
  • Confirm no deployment runs <2.5.27 or >=2.6.0,<2.6.10.
  • Verify port 9091 is not reachable from untrusted networks.
  • Review access logs around the metrics or management interface.
  • Confirm upgrade completion using approved asset and package records.
Prepared
Confidence
high
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-306: Credential and account abuse lookup

Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-26190 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2026-26190Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
milvus-iomilvus< 2.5.27, >= 2.6.0, < 2.6.10Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-306 · source CWE mapping

Missing Authentication for Critical Function

Missing Authentication for Critical Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.