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.
References
| Link | Resource |
|---|---|
| https://www.mongodb.com/docs/bi-connector/current/release-notes/ | Vendor Advisory |
Configurations
History
29 Sep 2026, 19:14
| Type | Values Removed | Values Added |
|---|---|---|
| References | () https://www.mongodb.com/docs/bi-connector/current/release-notes/ - Vendor Advisory | |
| CPE | cpe:2.3:a:mongodb:bi_connector:*:*:*:*:*:*:*:* | |
| First Time |
Mongodb bi Connector
Mongodb |
Information
Published : 2026-08-28 22:16
Updated : 2026-09-29 19:14
NVD link : CVE-2026-81517
Mitre link : CVE-2026-81517
CVE.ORG link : CVE-2026-81517
JSON object : View
Products Affected
mongodb
- bi_connector
CWE
CWE-248
Uncaught Exception
