The vulnerability is an improper error‑handling flaw that causes the entire mongosqld process to terminate when the configured log path cannot accept writes or perform rotation. An unauthenticated party able to communicate with the connector port can flood the service with routine connection logs until the underlying storage is exhausted, which triggers the crash. The flaw leads to denial of service for all users of the SQL interface because the shared process dies and does not restart until sufficient storage space is available. The weakness fits the CWE-248 category of failing to properly handle unexpected runtime errors.

Affected system is the MongoDB Connector for BI (mongosqld), the component that translates SQL queries to MongoDB operations. All released versions published by MongoDB prior to a vendor‑supplied patch are impacted. The flaw exists wherever the connector’s service port can be reached by an unauthenticated user. Because no precise version thresholds are listed, operators should treat all current deployments as vulnerable until an official fix is applied.

With a CVSS score of 8.7, this vulnerability is rated high severity and primarily threatens availability. EPSS data is unavailable and the flaw is not listed in CISA’s KEV catalog, indicating no publicly documented exploits as of now. The likely attack vector is network‑based, inferred from the description that an unauthenticated party able to reach the connector port can generate the excessive log activity that triggers the denial of service.