GHSA-jh6h-v6mp-h22v is a medium-severity (CVSS 4.5) Broken Cryptographic Algorithm vulnerability in github.com/milvus-io/milvus. A fix is available for github.com/milvus-io/milvus — see the affected versions and patch details below.
milvus: RBAC grantee-id uses truncated MD5 (64-bit), enabling privilege-binding collisions and cross-role privilege forgery
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for GHSA-jh6h-v6mp-h22v.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-jh6h-v6mp-h22v by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 379,842 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
github.com/milvus-io/milvusReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/milvus-io/milvus | all versions | 0.10.3-0.20260602041816-3d932f1c3e06go get github.com/milvus-io/milvus@v0.10.3-0.20260602041816-3d932f1c3e06 |
Affected Products
milvusmilvusDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/milvus-io/milvus, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/milvus-io/milvus to 0.10.3-0.20260602041816-3d932f1c3e06 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jh6h-v6mp-h22v is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is GHSA-jh6h-v6mp-h22v in your dependencies?
Find it across Go, including transitive dependencies.