CVE-2026-10814

HIGHNVD 7.07.0
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.0 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 99% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Elevated
7.0
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.0Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.0
EG Score
7.0(medium)
EG Risk
48(Track)
EG Risk 48/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity70% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
0.5%
KEV
Not listed

Published

June 4, 2026

Last Modified

July 22, 2026

Advisory Details (4)

Auto-updated Jun 12, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit, github_pr.
github_pr

fix: [RBAC] use full-length grantee ID hash

Fix merged in milvus-io/milvus PR #50060 on 2026-06-02 — awaiting tagged release

https://github.com/milvus-io/milvus/pull/50060
generic

[Bug]: RBAC grantee-id uses truncated MD5 (64-bit), enabling privilege-binding collisions and cross-role privilege forgery · Issue #49857 · milvus-io/milvus · GitHub

https://github.com/milvus-io/milvus/issues/49857
github_commit

commit 3d932f1c3e06 (milvus-io/milvus)

Fix landed in milvus-io/milvus commit 3d932f1c3e06 — awaiting tagged release

https://github.com/milvus-io/milvus/commit/3d932f1c3e065351c4440c27abe1e6479752544d
generic

GitHub - milvus-io/milvus: Milvus is a high-performance, cloud-native vector database built for scalable vector ANN search · GitHub

https://github.com/milvus-io/milvus/

Vendor Advisories for CVE-2026-10814(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 38× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 03:04 UTCEG score recompute 2.50
  2. 2026-07-22 14:08 UTCEPSS rescore
  3. 2026-07-21 15:24 UTCEPSS rescore
  4. 2026-07-20 17:08 UTCEPSS rescore
  5. 2026-07-18 10:04 UTCEPSS rescore
  6. 2026-07-16 17:02 UTCEPSS rescore
  7. 2026-07-15 16:57 UTCEPSS rescore
  8. 2026-07-14 03:23 UTCGHSA enrichment
  9. 2026-07-13 22:30 UTCEPSS rescore
  10. 2026-07-12 05:46 UTCEPSS rescore
  11. 2026-07-11 12:06 UTCGHSA enrichment
  12. 2026-07-11 08:27 UTCEPSS rescore
  13. 2026-07-08 15:15 UTCEPSS rescore
  14. 2026-07-08 15:15 UTCEPSS rescore
  15. 2026-07-08 09:41 UTCGHSA enrichment
  16. 2026-07-07 13:46 UTCEPSS rescore
  17. 2026-07-06 16:27 UTCEPSS rescore
  18. 2026-07-06 02:55 UTCGHSA enrichment
  19. 2026-07-06 02:23 UTCEPSS rescore
  20. 2026-07-05 02:30 UTCEPSS rescore
  21. 2026-07-05 02:30 UTCEPSS rescore
  22. 2026-07-03 21:34 UTCGHSA enrichment
  23. 2026-07-02 21:03 UTCGHSA enrichment
  24. 2026-07-01 20:29 UTCGHSA enrichment
  25. 2026-07-01 15:06 UTCEPSS rescore
Show 52 more
  1. 2026-07-01 15:06 UTCEPSS rescore
  2. 2026-06-30 20:05 UTCGHSA enrichment
  3. 2026-06-29 09:59 UTCGHSA enrichment
  4. 2026-06-28 14:07 UTCEPSS rescore
  5. 2026-06-28 04:56 UTCEPSS rescore
  6. 2026-06-28 04:56 UTCEPSS rescore
  7. 2026-06-28 04:19 UTCGHSA enrichment
  8. 2026-06-27 03:54 UTCGHSA enrichment
  9. 2026-06-26 03:30 UTCGHSA enrichment
  10. 2026-06-25 03:04 UTCGHSA enrichment
  11. 2026-06-24 14:05 UTCEPSS rescore
  12. 2026-06-24 02:40 UTCGHSA enrichment
  13. 2026-06-23 21:32 UTCEPSS rescore
  14. 2026-06-23 02:16 UTCGHSA enrichment
  15. 2026-06-21 01:59 UTCEPSS rescore
  16. 2026-06-21 01:59 UTCEPSS rescore
  17. 2026-06-19 23:49 UTCGHSA enrichment
  18. 2026-06-19 19:25 UTCEPSS rescore
  19. 2026-06-18 22:15 UTCGHSA enrichment
  20. 2026-06-18 17:52 UTCEPSS rescore
  21. 2026-06-17 21:51 UTCGHSA enrichment
  22. 2026-06-17 17:53 UTCEPSS rescore
  23. 2026-06-16 21:26 UTCGHSA enrichment
  24. 2026-06-15 21:02 UTCGHSA enrichment
  25. 2026-06-15 17:48 UTCEPSS rescore
  26. 2026-06-14 23:18 UTCEPSS rescore
  27. 2026-06-14 20:31 UTCGHSA enrichment
  28. 2026-06-13 23:00 UTCEPSS rescore
  29. 2026-06-13 23:00 UTCEPSS rescore
  30. 2026-06-13 20:06 UTCGHSA enrichment
  31. 2026-06-12 23:12 UTCEPSS rescore
  32. 2026-06-12 19:38 UTCGHSA enrichment
  33. 2026-06-11 19:14 UTCGHSA enrichment
  34. 2026-06-11 14:00 UTCEPSS rescore
  35. 2026-06-10 22:18 UTCEPSS rescore
  36. 2026-06-10 19:18 UTCNVD updateCVSS v3 → 7 · severity → HIGH
  37. 2026-06-10 18:50 UTCGHSA enrichment
  38. 2026-06-10 13:22 UTCEPSS rescore
  39. 2026-06-09 18:26 UTCGHSA enrichment
  40. 2026-06-08 18:01 UTCGHSA enrichment
  41. 2026-06-08 14:17 UTCEPSS rescore
  42. 2026-06-08 14:17 UTCEPSS rescore
  43. 2026-06-07 16:53 UTCGHSA enrichment
  44. 2026-06-07 15:25 UTCEPSS rescore
  45. 2026-06-07 15:24 UTCEPSS rescore
  46. 2026-06-06 16:28 UTCGHSA enrichment
  47. 2026-06-06 13:47 UTCEPSS rescore
  48. 2026-06-06 13:47 UTCEPSS rescore
  49. 2026-06-06 13:47 UTCEPSS rescore
  50. 2026-06-05 22:47 UTCEPSS rescore
  51. 2026-06-05 16:04 UTCGHSA enrichment
  52. 2026-06-04 15:40 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-10814?
CVE-2026-10814 is a high vulnerability published on June 4, 2026. 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…
When was CVE-2026-10814 disclosed?
CVE-2026-10814 was first published in the National Vulnerability Database on June 4, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-10814 actively exploited?
CVE-2026-10814 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-10814?
CVE-2026-10814 has a CVSS v3 base score of 7.0 (NVD).
How do I remediate CVE-2026-10814?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-10814, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-10814

Explore →

Is Your Infrastructure Affected by CVE-2026-10814?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.