MongoDB C# Driver up to 3.14.0 Connection Configuration information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.9 | $0-$5k | 0.00+ |
Summary
A vulnerability identified as problematic has been detected in MongoDB C# Driver up to 3.14.0. This vulnerability affects unknown code of the component Connection Configuration. The manipulation leads to information disclosure. This vulnerability is traded as CVE-2026-129936. An attack has to be approached locally. There is no exploit available. You should upgrade the affected component.
Details
A vulnerability was found in MongoDB C# Driver up to 3.14.0. It has been rated as problematic. This issue affects some unknown functionality of the component Connection Configuration. The manipulation with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality. The summary by CVE is:
A MongoDB C# Driver component that interprets connection configuration supplied by the hosting application can include the caller-supplied configuration value in the text of the error it raises when that value cannot be interpreted. The redaction applied to that text does not cover all forms in which secret material may appear, so authentication material embedded in the configuration value can be preserved in the resulting error text and in anything that records it. Exploitation requires only the low privilege needed to observe the application's own error output or logs on the system where the driver runs; no database credentials or server connectivity are required. The result is disclosure of sensitive information to parties whose access to error output is broader than their intended access to the configuration secret.
The advisory is shared at jira.mongodb.org. The identification of this vulnerability is CVE-2026-129936 since 11/16/2026. The exploitation is known to be easy. An attack has to be approached locally. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
Upgrading to version 3.14.1 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 4.0VulDB Meta Temp Score: 3.9
VulDB Base Score: 3.3
VulDB Temp Score: 3.2
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 4.7
CNA Vector (mongodb): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: C# Driver 3.14.1
Timeline
11/16/2026 CVE reserved11/19/2026 Advisory disclosed
11/19/2026 VulDB entry created
11/19/2026 VulDB entry last update
Sources
Advisory: jira.mongodb.orgStatus: Confirmed
CNA: mongodb
CVE: CVE-2026-129936 (🔒)
GCVE (CVE): GCVE-0-2026-129936
GCVE (VulDB): GCVE-100-440729
Entry
Created: 11/19/2026 21:22Changes: 11/19/2026 21:22 (76)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.