CVE-2025-64513: GO-2025-4114 - Milvus Proxy has a Critical Authentication Bypass Vulnerability in github.com/milvus-io/milvus

CVE-2025-64513 · Severity: medium · CVSS 4 · Published 2025-11-17

Milvus Proxy has a Critical Authentication Bypass Vulnerability in github.com/milvus-io/milvus

Technologies: github.com/milvus-io/milvus (Go). Vendors: Go.

Quick answers

Is CVE-2025-64513 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2025-64513 being exploited in the wild.
How severe is CVE-2025-64513?
Medium severity, with a CVSS score of 4, published 17 November 2025.
Which products and versions are affected?
github.com/milvus-io/milvus (Go) SEMVER:introduced=0,fixed=0.10.3-0.20251107071934-6102f001a971,introduced=0.10.4, SEMVER:introduced=0.10.4,fixed=2.4.24.
Is there a fix for CVE-2025-64513?
Yes. github.com/milvus-io/milvus (Go): upgrade to 0.10.3-0.20251107071934-6102f001a971, 2.4.24 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2025-64513?
Check whether you run github.com/milvus-io/milvus (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/milvus-io/milvus (Go): upgrade to 0.10.3-0.20251107071934-6102f001a971, 2.4.24 or later
    go get github.com/milvus-io/milvus@v2.4.24

Affected products

  • github.com/milvus-io/milvus (Go) SEMVER:introduced=0,fixed=0.10.3-0.20251107071934-6102f001a971,introduced=0.10.4, SEMVER:introduced=0.10.4,fixed=2.4.24

Identifiers

  • CVE-2025-64513
  • GHSA-mhjq-8c7m-3f7p
  • GO-2025-4114

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.