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.
References
| Link | Resource |
|---|---|
| https://www.mongodb.com/docs/bi-connector/current/release-notes/ | Vendor Advisory |
Configurations
History
29 Sep 2026, 19:14
| Type | Values Removed | Values Added |
|---|---|---|
| First Time |
Mongodb bi Connector
Mongodb |
|
| References | () https://www.mongodb.com/docs/bi-connector/current/release-notes/ - Vendor Advisory | |
| CPE | cpe:2.3:a:mongodb:bi_connector:*:*:*:*:*:*:*:* |
Information
Published : 2026-08-28 22:16
Updated : 2026-09-29 19:14
NVD link : CVE-2026-81518
Mitre link : CVE-2026-81518
CVE.ORG link : CVE-2026-81518
JSON object : View
Products Affected
mongodb
- bi_connector
CWE
CWE-295
Improper Certificate Validation
