Vulnerability in milvus (CVE-2026-10814)
Summary
Vulnerability in milvus (CVE-2026-10814). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.6.14 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-10814 has been found in milvus.
Risk of unauthorized operations or information disclosure. CVSS score: 4.5/10.
What to do: upgrade milvus to 2.6.14 or later.
If unsure, ask your IT team or search "milvus CVE-2026-10814" on the vendor's site.
CVE-2026-10814 (milvus) — CWE-327 / CVSS v3 4.5
Attack vector: local / no user interaction
Patched: 2.6.14 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-327) exists in milvus.
Check the vendor advisory for the affected versions of milvus.
Severity: Medium (CVSS 4.5/10). Risk of unauthorized operations or information disclosure.
Update to 2.6.14.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'milvus' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'milvus' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
milvusを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade milvus to 2.6.14ステージング環境で 2.6.14 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory vuldb.com
- advisory vuldb.com
- advisory vuldb.com
- advisory nvd.nist.gov
- advisory github.com
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- report github.com
- report vuldb.com
- web github.com