CVE-2026-81517: MongoDB Connector for BI Improper Error Handling of Log Write Failures May Cause Loss of SQL Service
MongoDB · BI Connector
Vendor fix available · Affected: MongoDB BI Connector · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 40% of scored CVEs
DescriptionCVE.org
An unauthenticated party able to reach the port of a MongoDB Connector for BI (mongosqld) instance may generate enough routine connection log activity to exhaust the storage backing the configured log path. When a log write or log rotation operation subsequently fails, the resulting error is not handled and the shared mongosqld process ends, ending service for all connected SQL clients. The process continues to end on startup until an operator restores available storage, and the diagnostic message explaining the condition is not recorded.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- MongoDB · BI Connectorbefore 2.14.31
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- MongoDB
- Published
- August 2026
CoverageNo articles yet
No CyberSIXT article names CVE-2026-81517 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.