CVE-2026-81517
Unauthenticated log-flood can exhaust disk and crash mongosqld, causing persistent service outage.
Is CVE-2026-81517 being exploited?
Not confirmed. CVE-2026-81517 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.26% probability of exploitation in the next 30 days.
How severe is CVE-2026-81517?
CVE-2026-81517 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-81517?
Yes. A fix has been recorded for CVE-2026-81517. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-81517 affect?
CVE-2026-81517 affects MongoDB Connector for BI (mongosqld). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-81517?
Apply vendor patch, restrict network access to mongosqld, ensure sufficient log storage/rotation.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote unauthenticated attacker can generate connection log activity to exhaust log storage, causing mongosqld to exit and persistent denial-of-service for SQL clients.
Immediate action required
- affected< 2.14.31
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.