Skip to content

← Public intelligence

Go package

github.com/milvus-io/milvus

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

3 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Low, CVSS 1.1GoPublished

    milvus: RBAC grantee-id uses truncated MD5 (64-bit), enabling privilege-binding collisions and cross-role privilege forgery

    CVE-2026-10814 · GHSA-jh6h-v6mp-h22v

    Affected
    • Go github.com/milvus-io/milvus < 0.10.3-0.20260602041816-3d932f1c3e06
    Fixed in
    0.10.3-0.20260602041816-3d932f1c3e06· Vendor fix available
    Issue
    A vulnerability has been found in milvus-io milvus up to 2.6.13. This vulnerability affects unknown code of the file internal/metastore/kv/rootcoord/kvcatalog.go of the component Grantee ID Hash Handler. The manipulation leads to use of weak hash. The attack needs to be performed locally. The attack's complexity is rated as high. It is stated that the exploitability is difficult. The exploit has been disclosed to the public and may be used. The identifier of the patch is 3d932f1c3e065351c4440c27abe1e6479752544d. Applying a patch is the recommended action to fix this issue.

    Recommended action: Upgrade to 0.10.3-0.20260602041816-3d932f1c3e06 (pre-release) or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. Critical, CVSS 9.8GoAmendedPublished

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

    CVE-2026-26190 · GHSA-7ppg-37fh-vcr6

    Affected
    • Go github.com/milvus-io/milvus < 2.5.27; >= 2.6.0, < 2.6.10
    Fixed in
    2.5.272.6.10· Vendor fix available
    Issue
    Milvus exposes TCP port 9091 by default with two critical authentication bypass vulnerabilities: 1. The /expr debug endpoint uses a weak, predictable default authentication token derived from etcd.rootPath (default: by-dev), enabling arbitrary expression evaluation. 2. 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. Details Vulnerability 1: Weak Default Authentication on /expr Endpoint The /expr endpoint on port 9091 accepts an auth parameter that defaults to the etcd.rootPath value (by-dev). This value is well-known and predictable. An attacker who can reach port 9091 can evaluate arbitrary internal Go expressions, leading to: - Information/Credential Disclosure: Reading internal configuration values (MinIO secrets, etcd credentials) and user credential hashes via param.MinioCfg.SecretAccessKey.GetValue(),…

    Recommended action: Upgrade to 2.6.10 or 2.5.27 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  3. Critical, CVSS 9.3GoPublished

    Milvus Proxy has a Critical Authentication Bypass Vulnerability

    CVE-2025-64513 · GHSA-mhjq-8c7m-3f7p

    Affected
    • Go github.com/milvus-io/milvus >= 0.10.4, < 2.4.24; >= 2.5.0, < 2.5.21; >= 2.6.0, < 2.6.5; < 0.10.3-0.20251107071934-6102f001a971
    Fixed in
    0.10.3-0.20251107071934-6102f001a9712.5.212.6.52.4.24· Vendor fix available
    Issue
    Impact 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. Patches Has the problem been patched? What versions should users upgrade to? This issue has been fixed in the following versions: • Milvus 2.4.24 • Milvus 2.5.21 • Milvus 2.6.5 Users should upgrade to these patched versions or later to mitigate the vulnerability. Workarounds 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…

    Recommended action: Upgrade to 2.6.5, 2.5.21, 2.4.24 or 0.10.3-0.20251107071934-6102f001a971 (pre-release) by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →