CVE-2026-81518

BI Connector Optional Client Certificate Verification Allows Unauthenticated Connections

Published Aug 28, 2026 CVSS 4.0 · 8.7 High EPSS < 1% KEV · Not listed
Description
When mongosqld is configured with a client certificate authority file, the listener requests a client certificate during the TLS handshake but does not require one, so a client that presents no certificate is still accepted. In deployments that rely on client certificates as the sole means of identifying users, a remote party with network access to the listener can therefore establish a session and read the MongoDB data exposed through the connector.

Analysis

AI-generated

Technical impact

mongosqld requests but does not enforce a client certificate during TLS handshakes when a CA file is configured, resulting in a Client Certificate Verification Failure (CWE‑295). In environments that rely solely on client certificates for authentication, a party that can reach the listener can connect without presenting a certificate and instantly gain access to data exposed through the connector, causing a breach of confidentiality.

Affected Systems

MongoDB BI Connector with client‑certificate authentication enabled. No specific versions are listed, so all releases that allow a CA file and do not enforce client certs are potentially vulnerable.

Risk and Exploitability

The CVSS score of 8.7 classifies this as a high‑severity vulnerability. The EPSS score is not available, and it is not yet listed in CISA’s KEV catalog. The likely attack vector is remote network access to the BI Connector listener: a malicious actor can initiate a TLS connection, omit a certificate, and when the server does not enforce it, obtain an unauthorized session that can read exposed MongoDB data.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to the latest MongoDB BI Connector release that enforces client certificates during TLS handshakes.
  • Configure the connector to disallow connections that lack a client certificate, ensuring strict client‑auth enforcement.
  • Limit network exposure of the BI Connector listener to trusted hosts only, reducing the opportunity for an attacker to initiate the connection.

Generated by OpenCVE AI on August 29, 2026 at 00:23 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
CPEs cpe:2.3:a:mongodb:bi_connector:*:*:*:*:*:*:*:*
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Mongodb
Mongodb bi Connector
Vendors & Products Mongodb
Mongodb bi Connector
Type Values Removed Values Added
Description When mongosqld is configured with a client certificate authority file, the listener requests a client certificate during the TLS handshake but does not require one, so a client that presents no certificate is still accepted. In deployments that rely on client certificates as the sole means of identifying users, a remote party with network access to the listener can therefore establish a session and read the MongoDB data exposed through the connector.
Title BI Connector Optional Client Certificate Verification Allows Unauthenticated Connections
Weaknesses CWE-295
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N'}

cvssV4_0

{'score': 8.7, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-295

    Improper Certificate Validation

Sources

Status
PUBLISHED
Assigner
mongodb
Published
Updated
Aug 31, 2026, 6:38 PM
Reserved
Aug 26, 2026, 10:07 PM
Status
Analyzed
Published
Aug 28, 2026, 10:16 PM
Modified
Sep 29, 2026, 7:14 PM