milvus-io Milvus up to 2.6.22/3.0.0 Service Components /management/stop role resource consumption

Summaryinfo

A vulnerability classified as problematic has been found in milvus-io Milvus up to 2.6.22/3.0.0. Affected is an unknown function of the file /management/stop of the component Service Components. Performing a manipulation of the argument role results in resource consumption. This vulnerability is known as CVE-2026-69111. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability was found in milvus-io Milvus up to 2.6.22/3.0.0. It has been classified as problematic. This affects some unknown processing of the file /management/stop of the component Service Components. The manipulation of the argument role with an unknown input leads to a resource consumption vulnerability. CWE is classifying the issue as CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. This is going to have an impact on availability. The summary by CVE is:

Milvus through 2.6.22 and 3.0.0 contains an unauthenticated denial of service vulnerability that allows remote attackers to terminate service components by sending a crafted HTTP GET request to the management server on port 9091. Attackers can exploit the unprotected /management/stop endpoint, which bypasses REST API authentication middleware, by supplying a 'role' parameter to shut down the proxy, datanode, or querynode components, resulting in denial of service.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-69111 since 08/03/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1499 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• milvus-io

Name

• Milvus

Version

• 2.6.0
• 2.6.1
• 2.6.2
• 2.6.3
• 2.6.4
• 2.6.5
• 2.6.6
• 2.6.7
• 2.6.8
• 2.6.9
• 2.6.10
• 2.6.11
• 2.6.12
• 2.6.13
• 2.6.14
• 2.6.15
• 2.6.16
• 2.6.17
• 2.6.18
• 2.6.19
• 2.6.20
• 2.6.21
• 2.6.22
• 3.0

Website

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

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion