CVE-2026-25628
Privilege escalation via /logger; attacker can append to arbitrary files in Qdrant prior to 1.16.0.
Is CVE-2026-25628 being exploited?
Not confirmed. CVE-2026-25628 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.51% probability of exploitation in the next 30 days.
How severe is CVE-2026-25628?
CVE-2026-25628 is rated High with a CVSS score of 8.5. 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-25628?
Yes. A fix has been recorded for CVE-2026-25628. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-25628 affect?
CVE-2026-25628 affects Qdrant Vector DB (v1.9.3–v1.15.x). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-25628?
Upgrade to 1.16.0+ to fix the issue.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Arbitrary file write via /logger; may corrupt configs or logs and enable further abuse or local escalation.
Patch when possible
- affected>= 1.9.3 and < 1.16.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.