CVE-2026-81517

Awaiting Analysis Awaiting Analysis - Queue

MongoDB Connector for BI Log Exhaustion DoS

Publication date: 2026-08-28

Last updated on: 2026-08-31

Assigner: MongoDB, Inc.

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-08-28

Last Modified

2026-08-31

Generated

2026-09-18

AI Q&A

2026-08-29

EPSS Evaluated

2026-09-15

NVD

CVE-2026-81517

EUVD

EUVD-2026-67933

Affected Vendors & Products

Vendor	Product	Version / Range
mongodb	mongodb_connector_for_bi	*

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-248	An exception is thrown from a function, but it is not caught.

Attack-Flow Graph

Executive Summary

This vulnerability allows an unauthenticated attacker to connect to a MongoDB Connector for BI (mongosqld) instance and generate excessive log activity. This can fill up the storage where logs are stored, causing log write or rotation failures. When this happens, the mongosqld process crashes and stops serving all connected SQL clients until storage is restored.

Detection Guidance

Monitor the log path storage usage for the MongoDB Connector for BI (mongosqld) instance. Check for repeated connection log activity that may indicate an attempt to exhaust storage. Verify if the mongosqld process terminates unexpectedly due to log write or rotation failures.

Impact Analysis

If you use MongoDB Connector for BI, an attacker could exploit this to disrupt service for all SQL clients connected through the mongosqld instance. This results in downtime and loss of access to data until the storage issue is resolved.

Compliance Impact

This vulnerability could impact compliance with GDPR and HIPAA by causing service disruptions due to log storage exhaustion, potentially leading to unauthorized data access or processing interruptions. Unhandled errors and process termination may violate availability requirements in these regulations.

Mitigation Strategies

Ensure sufficient storage is available for the log path of the mongosqld instance. Implement monitoring to detect log storage exhaustion early. Restart the mongosqld process after restoring storage to resume service. Consider adjusting log rotation settings to prevent rapid storage consumption.

Hi! I’m here to help you understand CVE-2026-81517. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70