CVE-2026-10814: A vulnerability has been found in milvus-io milvus up to 2.6.13

Q: How do I fix CVE-2026-10814?

milvus: upgrade to newer than 2.6.13. Exact commands for each OS are on this page.

Q: Is CVE-2026-10814 being exploited?

CVE-2026-10814 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-10814 affect?

CVE-2026-10814 affects milvus. Severity is medium (CVSS 4.5). 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 we

Q: How urgent is CVE-2026-10814?

Priority 16/100. No elevated risk signals yet.

Routine

MEDIUM 4.5UPGRADE

CVE-2026-10814 is a medium-severity flaw (CVSS 4.5) affecting milvus. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	4.5 (Medium)
Attack vector	Local
Attack complexity	High
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.1% (top 100%)
CISA exploited list	No
Weakness	CWE-327, CWE-328
Published	2026-06-04
Last modified	2026-07-22

Publisher (CNA): VulDB · Vendor: milvus

Last updated 2026-07-22 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-06-04 16:16 UTCPublished CVE record published
2026-07-22 20:10 UTCUpdated Record last modified

milvus milvus UPGRADE

Affected: <= 2.6.13

Fixed in: newer than 2.6.13

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy milvus || rpm -q milvus || milvus --version

2. UPGRADE to newer than 2.6.13 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade milvus

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade milvus

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-10814?

milvus: upgrade to newer than 2.6.13. Exact commands for each OS are on this page.

Is CVE-2026-10814 being exploited?

CVE-2026-10814 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-10814 affect?

CVE-2026-10814 affects milvus. Severity is medium (CVSS 4.5). 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 we

How urgent is CVE-2026-10814?

Priority 16/100. No elevated risk signals yet.

References

← Back to latest CVEs