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

Advisory record · `GHSA-jh6h-v6mp-h22v`

- **Identifiers:** `GHSA-jh6h-v6mp-h22v` · `BIT-milvus-2026-10814` · `CVE-2026-10814` · `GO-2026-5999`
- **State:** Confirmed
- **Severity:** CVSS 2.0 Low
- **Critical:** No
- **Weakness (CWE):** [CWE-327](https://cwe.mitre.org/data/definitions/327.html) · [CWE-328](https://cwe.mitre.org/data/definitions/328.html)
- **Tags:** [Weak cryptography or TLS](https://agentprime.io/advisories/tag/weak-crypto.md)
- **Published:** 4 Jun 2026
- **Updated:** 21 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 4 Jun 2026, 18:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/milvus-io/milvus` (Go): affected `<0.10.3-0.20260602041816-3d932f1c3e06`; fixed in `0.10.3-0.20260602041816-3d932f1c3e06`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> milvus versions before 0.10.3-0.20260602041816-3d932f1c3e06 use a truncated 64-bit MD5 hash for RBAC grantee IDs, allowing hash collisions that can bind privileges to the wrong role. A local attacker with high attack complexity could forge privileges across roles. Upgrade to 0.10.3-0.20260602041816-3d932f1c3e06 or later.

Written 6 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 2.0 Low, CVSS 4.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`, from CNA (VulDB)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0009, the 1st percentile, on 12 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:05 UTC: First seen by agentprime
- 31 Oct 2026, 15:05 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-jh6h-v6mp-h22v)

## Sources

- [GitHub Advisory Database: GHSA-jh6h-v6mp-h22v](https://github.com/advisories/GHSA-jh6h-v6mp-h22v)
- [OSV: GHSA-jh6h-v6mp-h22v](https://osv.dev/vulnerability/GHSA-jh6h-v6mp-h22v)
- <https://nvd.nist.gov/vuln/detail/CVE-2026-10814>
- <https://github.com/milvus-io/milvus/issues/49857>
- <https://github.com/milvus-io/milvus/pull/50060>
- <https://github.com/milvus-io/milvus/commit/3d932f1c3e065351c4440c27abe1e6479752544d>
- <https://github.com/milvus-io/milvus>
- <https://vuldb.com/cve/CVE-2026-10814>
- <https://vuldb.com/submit/831645>
- <https://vuldb.com/vuln/368262>
- <https://vuldb.com/vuln/368262/cti>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-jh6h-v6mp-h22v>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-jh6h-v6mp-h22v/>. Everything for agents: <https://agentprime.io/llms.txt>.