CVE-2026-69111
Unauthenticated HTTP endpoint lets remote attacker stop Milvus components, causing DoS.
Is CVE-2026-69111 being exploited?
Not confirmed. CVE-2026-69111 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.57% probability of exploitation in the next 30 days.
How severe is CVE-2026-69111?
CVE-2026-69111 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-69111?
Not known from our data. No patch reference has been recorded for CVE-2026-69111, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-69111 affect?
CVE-2026-69111 affects Milvus <= 2.6.22, Milvus 3.0.0, Milvus management server (port 9091), proxy, datanode, querynode components. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-69111?
Restrict/deny access to port 9091, apply vendor patch when released.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated HTTP GET to /management/stop (port 9091) with 'role' param can remotely stop proxy, datanode, or querynode, causing service outage.
Immediate action required
- affected<= 2.6.22
- affected3.0.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.