milvus: Use of a Broken or Risky Cryptographic Algorithm
CVE-2026-10814 is a high-severity use of a broken or risky cryptographic algorithm vulnerability in milvus from Milvus-io, with a CVSS 3.1 base score of 7.0 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. Affected milvus versions: 2.6.0; 2.6.1; 2.6.2, and others listed below. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.09% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of milvus you run against the affected versions below, and install the vendor's latest release.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Milvus-io | milvus | 2.6.0; 2.6.1; 2.6.2; 2.6.3; 2.6.4; 2.6.5; 2.6.6; 2.6.7; and 6 more ranges | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- HighSuccess depends on conditions outside the attacker's control.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 1.1 | Low | CNA (vuldb.com) |
| CVSS 3.1 | 4.5 | Medium | CNA (vuldb.com) |
| CVSS 3.1 | 7.0 | High | NVD |
| CVSS 2.0 | 3.5 | Low | CNA (vuldb.com) |
Official 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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Use of a Broken or Risky Cryptographic Algorithm
The product uses a broken or risky cryptographic algorithm or protocol.
How developers prevent this class of flaw
- Ensure that the design allows one cryptographic algorithm to be replaced with another in the next generation or version. Where possible, use wrappers to make the interfaces uniform. This will make it easier to upgrade to stronger algorithms. With hardware, design the product at the Intellectual Property (IP) level so that one cryptographic algorithm can be replaced with another in the next generation of the hardware product.
- Carefully manage and protect cryptographic keys (see CWE-320). If the keys can be guessed or stolen, then the strength of the cryptography itself is irrelevant.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Industry-standard implementations will save development time and may be more likely to avoid errors that can occur during implementation of cryptographic algorithms. Consider the ESAPI Encryption feature.
More Use of a Broken or Risky Cryptographic Algorithm vulnerabilities (CWE-327)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Third-party and government advisories
- vuldb.com/cve/CVE-2026-10814Third Party Advisory, VDB Entry
- vuldb.com/submit/831645Third Party Advisory, VDB Entry
- vuldb.com/vuln/368262Third Party Advisory, VDB Entry
Other references
- github.com/milvus-io/milvus/Product
- github.com/milvus-io/milvus/issues/49857Issue Tracking
- vuldb.com/vuln/368262/ctiPermissions Required, VDB Entry
Other vulnerabilities in milvus
- 7.5 High severity
- 9.8 Critical severity
- 9.3 Critical severity
Recent Use of a Broken or Risky Cryptographic Algorithm vulnerabilities
- 7.4 High severity
- 9.1 Critical severity
- 9.2 Critical severity
- 7.3 High severity
- 7.5 High severity
- 7.5 High severity
Spotted an error? Tell us.