CVE-2026-26190
Milvus auth bypass on 9091 and unauthenticated /api/v1 access.
Is CVE-2026-26190 being exploited?
Not confirmed. CVE-2026-26190 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 37% probability of exploitation in the next 30 days.
How severe is CVE-2026-26190?
CVE-2026-26190 is rated Critical with a CVSS score of 9.8. 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-26190?
Yes. A fix has been recorded for CVE-2026-26190. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-26190 affect?
CVE-2026-26190 affects Milvus. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-26190?
Upgrade to 2.5.27+ or 2.6.10+; restrict exposure.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Auth bypass enables unauthenticated REST API access to data/credentials and execute expressions.
Patch when possible
- affected< 2.5.27
- affected>= 2.6.0 and < 2.6.10
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.