Is CVE-2026-10814 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-10814 being exploited in the wild.

How severe is CVE-2026-10814?

Medium severity, with a CVSS score of 4.5, published 4 June 2026.

Which products and versions are affected?

github.com/milvus-io/milvus (Go) < 0.10.3-0.20260602041816-3d932f1c3e06, SEMVER:introduced=0,fixed=0.10.3-0.20260602041816-3d932f1c3e06; Milvus < 0.10.3-0.20260602041816-3d932f1c3e06, up to 2.6.13.

Is there a fix for CVE-2026-10814?

Yes. github.com/milvus-io/milvus (Go): upgrade to 0.10.3-0.20260602041816-3d932f1c3e06 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-10814 attacked?

It is attacked with local access, in a software library.

Am I affected by CVE-2026-10814?

Check whether you run github.com/milvus-io/milvus (Go) or Milvus 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.

CVE-2026-10814: Milvus weak hash in RBAC Grantee ID Handler

Q: Is there a fix for CVE-2026-10814?

Yes. github.com/milvus-io/milvus (Go): upgrade to 0.10.3-0.20260602041816-3d932f1c3e06 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-10814 attacked?

It is attacked with local access, in a software library.

Q: Am I affected by CVE-2026-10814?

Check whether you run github.com/milvus-io/milvus (Go) or Milvus 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.

CVE-2026-10814 · Severity: medium · CVSS 4.5 · Published 2026-06-04

Milvus, an open-source vector database, contains a flaw in how it manages user permissions. The system uses a weak identification method for security roles that can lead to 'collisions,' where two different roles are mistakenly treated as the same. In practice, this could allow a user with limited access to gain the permissions of a more privileged role, potentially leading to unauthorized data access or modification.

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

Quick answers

Is CVE-2026-10814 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-10814 being exploited in the wild.
How severe is CVE-2026-10814?: Medium severity, with a CVSS score of 4.5, published 4 June 2026.
Which products and versions are affected?: github.com/milvus-io/milvus (Go) < 0.10.3-0.20260602041816-3d932f1c3e06, SEMVER:introduced=0,fixed=0.10.3-0.20260602041816-3d932f1c3e06; Milvus < 0.10.3-0.20260602041816-3d932f1c3e06, up to 2.6.13.
Is there a fix for CVE-2026-10814?: Yes. github.com/milvus-io/milvus (Go): upgrade to 0.10.3-0.20260602041816-3d932f1c3e06 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-10814 attacked?: It is attacked with local access, in a software library.
Am I affected by CVE-2026-10814?: Check whether you run github.com/milvus-io/milvus (Go) or Milvus 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.20260602041816-3d932f1c3e06 or later
```
go get github.com/milvus-io/milvus@v0.10.3-0.20260602041816-3d932f1c3e06
```

Technical details

A vulnerability exists in the Milvus RBAC (Role-Based Access Control) implementation within 'internal/metastore/kv/rootcoord/kv_catalog.go'. The system generates 'grantee-id' values by truncating MD5 hashes to 64 bits (16 hex characters). This short identifier length significantly increases the probability of hash collisions. An attacker with local access to the metadata store (e.g., etcd) or the ability to influence role/object names could cause two different authorization relationships to share the same identifier. This results in cross-role privilege forgery, where a victim role resolves the privilege subtree of a donor role. The issue is addressed in patch 3d932f1c3e065351c4440c27abe1e6479752544d.

Affected products

milvus-io milvus < 0.10.3-0.20260602041816-3d932f1c3e06

Identifiers

CVE-2026-10814
GHSA-jh6h-v6mp-h22v
GO-2026-5999

Timeline

2026-06-04: advisory
2026-06-04: disclosed
2026-07-15: patched

References

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