# CVE-2026-10814: milvus-io milvus Grantee ID Hash kv_catalog.go weak hash

> A local attacker with high complexity can exploit a weak hash in Milvus to potentially bypass security controls.

- **Severity:** Low 2.0 (`CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Jun 2026
- **Updated:** 4 Jun 2026
- **Also known as:** BIT-milvus-2026-10814, GHSA-jh6h-v6mp-h22v, GO-2026-5999

## What is CVE-2026-10814?

CVE-2026-10814 is a low-severity vulnerability in milvus-io milvus, published on 4 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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/kv_catalog.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.

Weakness: CWE-328 (Use of Weak Hash), CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

## Which versions are affected by CVE-2026-10814?

4 open source packages ship an affected version, including github.com/milvus-io/milvus and milvus. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/milvus-io/milvus` | Go | All versions | 0.10.3-0.20260602041816-3d932f1c3e06 |
| `github.com/milvus-io/milvus` | Go | All versions | 0.10.3-0.20260602041816-3d932f1c3e06 |
| `github.com/milvus-io/milvus` | Go | All versions | 0.10.3-0.20260602041816-3d932f1c3e06 |
| `milvus` | Bitnami | All versions | 2.6.14 |

Products: Milvus Milvus.

## How do I fix CVE-2026-10814?

Upgrade github.com/milvus-io/milvus to 0.10.3-0.20260602041816-3d932f1c3e06 or later.

## Is CVE-2026-10814 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-10814 exists.

## Other vulnerabilities in milvus-io milvus

- [CVE-2026-26190](https://insights.sbomify.com/CVE-2026-26190/): Milvus Allows Unauthenticated Access to Restful API on Metrics Port (9091) Leads to Critical System Compromise (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-10814 and fix it if it is affected.

What it is: CVE-2026-10814 is a low-severity vulnerability in milvus-io milvus, published on 4 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-10814 exists.

Affected packages and fixed versions:
- github.com/milvus-io/milvus (Go): affected all versions; fixed in 0.10.3-0.20260602041816-3d932f1c3e06
- github.com/milvus-io/milvus (Go): affected all versions; fixed in 0.10.3-0.20260602041816-3d932f1c3e06
- github.com/milvus-io/milvus (Go): affected all versions; fixed in 0.10.3-0.20260602041816-3d932f1c3e06
- milvus (Bitnami): affected all versions; fixed in 2.6.14

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-10814/ (Markdown: https://insights.sbomify.com/CVE-2026-10814/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-10814
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-10814
- OSV: https://osv.dev/vulnerability/CVE-2026-10814

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-10814/
Summaries are generated and may contain mistakes; the official description above is the record.