BI Connector Optional Client Certificate Verification Allows Unauthenticated Connections (CVE-2026-81518) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-81518

BI Connector Optional Client Certificate Verification Allows Unauthenticated Connections

Answer in brief

CVE-2026-81518 records a Unknown severity vulnerability in BI Connector Optional Client Certificate Verification Allows Unauthenticated Connections. The current sources do not mark it as known exploited. The current feed maps MongoDB/BI Connector (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 28, 2026Updated Aug 28, 2026Source checked Aug 28, 2026First seen by HOL Aug 28, 2026Material review Aug 28, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps MongoDB/BI Connector (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
MongoDB/BI Connectorgeneric	>=0 <2.14.31	2.14.31

Recommended response

Check inventory. Check lockfiles and deployed manifests for MongoDB/BI Connector.
Review the reported fix. Update MongoDB/BI Connector to 2.14.31 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Aug 28, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 28, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 28, 2026

Sources and claim methodology

Source referencemongodb.com

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.