Skip to main content
VulnerabilityPublished Updated

CVE-2026-26190: milvus · Missing Authentication

Affects milvusSource CVE Database V5

0

Not known to be exploited · public detection template (Nuclei) · 39% EPSS · CVSS 9.8 Critical : upgrade to 2.6.10 or 2.5.27 as a priority.

Data as of 26 Oct 2026, 09:16 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
39.2% chance of exploitation in 30 days – higher than 98% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.6.10, 2.5.27
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Feb 2026

  2. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  3. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  4. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade milvus to 2.6.10 or 2.5.27.

Affected software

ProductAffectedFixed in
milvus-iomilvusAffected
  • <2.5.27
  • >=2.6.0 <2.6.10
Fixed in
  • 2.6.10
  • 2.5.27

AI-suggested

Upgrade Milvus to version 2.5.27 or later, or 2.6.10 or later, where this vulnerability is fixed. No other mitigations are indicated by the vendor advisory. Patch status is confirmed fixed in these versions.

Description

Milvus versions prior to 2.5.27 and 2.6.10 have a critical authentication bypass vulnerability. The default TCP port 9091 exposes a debug endpoint (/expr) that uses a weak, predictable authentication token, allowing arbitrary expression evaluation. Additionally, the full REST API is accessible on the metrics/management port without authentication, enabling unauthenticated access to all business operations including data and credential management. This vulnerability is fixed in versions 2.5.27 and 2.6.10.

References

Community reviews

Loading reviews…