How severe is CVE-2026-81517?

CVE-2026-81517 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.

Is CVE-2026-81517 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (38th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-81517?

CVE-2026-81517 affects Mongodb Bi Connector. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-81517?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2026-81517 published?

CVE-2026-81517 was published on 2026-08-28 and last updated on 2026-09-29.

CVE-2026-81517

CVE-2026-81517 is a high-severity vulnerability in Mongodb Bi Connector with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-248.

Key facts

Severity: High (CVSS 3.x base score 7.5)
CVSS v4: 8.7
EPSS exploit prediction: 0% (38th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-248
Affected product: Mongodb Bi Connector
Published: 2026-08-28
Last modified: 2026-09-29

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.

Frequently asked questions

What is CVE-2026-81517?: 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.
How severe is CVE-2026-81517?: CVE-2026-81517 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.
Is CVE-2026-81517 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (38th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-81517?: CVE-2026-81517 affects Mongodb Bi Connector. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-81517?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2026-81517 published?: CVE-2026-81517 was published on 2026-08-28 and last updated on 2026-09-29.

References

https://www.mongodb.com/docs/bi-connector/current/release-notes/

Affected products (1)

cpe:2.3:a:mongodb:bi_connector:*:*:*:*:*:*:*:*

More vulnerabilities in Mongodb Bi Connector

CVE-2026-77586 — High (CVSS 8.0): In MongoDB Connector for BI, MongoDB object names such as collection, field, and index names are placed into the quoted…
CVE-2026-81490 — High (CVSS 7.7): A database user able to create a view in a namespace that MongoDB Connector for BI samples can cause the…
CVE-2026-81520 — High (CVSS 7.5): A network-reachable client that has not yet authenticated can hold a MongoDB Connector for BI authentication session…
CVE-2026-81518 — High (CVSS 7.5): When mongosqld is configured with a client certificate authority file, the listener requests a client certificate…
CVE-2026-75159 — Medium (CVSS 5.9): An unauthenticated client that can reach a MongoDB Connector for BI deployment configured with Kerberos authentication…
CVE-2026-77184 — Medium (CVSS 5.2): In MongoDB Connector for BI, the description text of a collection's JSON schema validator is incorporated into the…

All CVEs affecting Mongodb Bi Connector →

Other CWE-248 vulnerabilities

CVE-2018-11466 — Critical (CVSS 9.8): A vulnerability has been identified in SINUMERIK 808D V4.7 (All versions), SINUMERIK 808D V4.8 (All versions),…
CVE-2024-42037 — Critical (CVSS 9.3): Vulnerability of uncaught exceptions in the Graphics module Impact: Successful exploitation of this vulnerability may…
CVE-2025-53620 — Critical (CVSS 9.2): @builder.io/qwik-city is the meta-framework for Qwik. When a Qwik Server Action QRL is executed it dynamically load the…
CVE-2026-61666 — High (CVSS 8.9): websocket-driver is a WebSocket protocol handler with pluggable I/O. Prior to 0.8.2, WebSocket::Driver.server() passes…
CVE-2026-96277 — High (CVSS 8.7): Uncaught exception, Improper Handling of Exceptional Conditions vulnerability in Apache Thrift Ruby bindings. This…
CVE-2026-96294 — High (CVSS 8.7): Uncaught exception, Improper Handling of Exceptional Conditions vulnerability in Apache Thrift NodeJS bindings. This…

Browse all CWE-248 vulnerabilities →