Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify .NET application using MongoDB CSFLE
-
DeliveryGain read access to application log or aggregation platform
-
ExploitLocate plaintext KMS credentials in diagnostic output
-
ExecutionAuthenticate to KMS provider using recovered credentials
-
PersistUnwrap MongoDB data-encryption keys
-
ImpactDecrypt protected field data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A09:2025 - Security Logging & Alerting Failures
ASVS 5.0
V16 - Security Logging and Error Handling Log data sanitization
|
| Exploitation Conditions | Exploitation requires two concurrent conditions: (1) the target application must use the MongoDB C Driver with client-side field-level encryption (CSFLE) or Queryable Encryption actively configured, supplying KMS provider credentials via AutoEncryptionOptions or an equivalent configuration object - this is a non-default deployment mode not present in standard MongoDB .NET applications; and (2) the attacker must have read access to the application's log output, a log aggregation or SIEM platform ingesting those logs, or a process memory dump of the .NET application host. Exploitation is not possible against applications that do not configure client-side encryption, nor against deployments where log access is strictly controlled. Authentication requirements align with CVSS 4.0 PR:L - the attacker needs at minimum low-privileged access to the logging infrastructure, not unauthenticated remote access. |
| Impact | The CVSS 4.0 vector (AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/SC:H) accurately captures the threat model: local or log-system read access with low privileges is sufficient, but AT:P correctly constrains scope to deployments where CSFLE is actively configured - a non-default state for most MongoDB applications. The VC:H and SC:H ratings reflect that KMS credential exposure does not merely disclose one record but potentially all encrypted field data across every collection using those keys, an outsized secondary blast radius. EPSS data is absent from the provided intelligence, so numerical exploitation probability cannot be stated; however, the bounded attack surface (log access plus CSFLE configuration) keeps real-world exploitation likelihood lower than a network-exploitable credential leak. KEV status is unconfirmed and no POC is known. The practical priority is highest for organizations that (a) use CSFLE or Queryable Encryption and (b) aggregate application logs in platforms accessible to broader teams - where leaked KMS credentials could be silently harvested from historical log archives. |
| Exploit ScenarioDerived | An attacker with read access to a centralized log aggregation system queries stored application logs from a .NET service that uses the MongoDB C Driver with CSFLE configured. The driver's diagnostic output of its client settings object appears in the logs with AWS KMS access keys or Azure client secrets reproduced in plaintext. The attacker extracts these credentials and uses them directly against the AWS KMS or Azure Key Vault API to unwrap the data-encryption keys, then decrypts protected MongoDB field values entirely outside the application's access controls. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 27, 2026
Sensitive KMS provider credentials supplied for client-side field-level encryption (CSFLE) in the MongoDB C
Driver are reproduced in plaintext within the driver's diagnostic string representation of its client settings, rather than being masked like other secret fields. Any party with read access to application logs, diagnostic output, or process memory dumps can recover these credentials and independently invoke the key management service to unwrap data-encryption keys, compromising all data protected by those keys. No public exploit code or active exploitation in CISA KEV has been identified at time of analysis; exploitation is bounded by the requirement that CSFLE be configured and that the attacker have access to diagnostic output.
RemediationAI
The primary fix is to upgrade the MongoDB C
Driver (MongoDB.Driver NuGet package) to version 3.11.1 or later, available at https://www.nuget.org/packages/MongoDB.Driver/3.11.1. Before or alongside patching, restrict read access to application log files and any log aggregation platforms (Splunk, Elasticsearch, Datadog, etc.) to the minimum necessary personnel, as logs generated by vulnerable driver versions may already contain exposed credentials. Rotate all KMS provider credentials - AWS IAM access keys, Azure service principal client secrets, GCP service account key files, or local master key material - that were active while vulnerable driver versions were running, since prior log archives may already contain them. Where possible, audit and purge or redact log archives that captured driver diagnostic output during the vulnerable period. If immediate upgrade is not feasible, suppress or filter diagnostic serialization of the MongoDB client settings object at the logging framework layer as a temporary measure, though this carries the trade-off of reduced observability.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The MongoDB C
Driver (NuGet package MongoDB.Driver) implements client-side field-level encryption (CSFLE) and Queryable Encryption, allowing applications to encrypt field values before they reach the database server. The driver accepts KMS provider credentials - AWS IAM keys, Azure service principal secrets, GCP service account keys, or local master key material - as part of its AutoEncryptionOptions configuration object. CWE-532 (Insertion of Sensitive Information into Log File) identifies the root cause: the driver's diagnostic serialization path (e.g., a ToString() override or structured logging formatter for the client settings object) faithfully reproduces these credential fields verbatim, while other secrets in the same configuration are correctly masked. The CPE cpe:2.3:a:mongodb:c#_driver:*:*:*:*:*:*:*:* covers all driver versions without a lower bound, indicating the flaw may span a wide range of releases prior to the fix.
Know when MongoDB gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N
Local log read access with low privileges is sufficient; scope changes because recovered KMS credentials compromise encrypted data in an external key management system.
Primary rating from Vendor (mongodb).
CVSS VectorVendor: mongodb
Lifecycle Timeline
1DescriptionCVE.org
A weakness in the client-side encryption configuration surface of the MongoDB C
Driver causes sensitive key-management credential material supplied by the application to be reproduced verbatim in the driver's human-readable diagnostic representation of its client settings, instead of being masked as other secret fields are. A party able to read the application's logs, diagnostic output, or a process memory dump may thereby recover the plaintext credentials and use them to decrypt protected field data.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
MongoDB before 2.0.9 and 2.2.x before 2.2.4 does not properly validate requests to the nativeHelper function in SpiderMo
The find prototype in scripting/engine_v8.h in MongoDB 2.4.0 through 2.4.4 allows remote authenticated users to cause a
The MongoDB bson JavaScript module (also known as js-bson) versions 0.5.0 to 1.0.x before 1.0.5 is vulnerable to a Regul
Remote code execution in Chartbrew versions prior to 4.8.1 allows authenticated attackers with high privileges to execut
After user deletion in MongoDB Server the improper invalidation of authorization sessions allows an authenticated user's
The default configuration for MongoDB before 2.3.2 does not validate objects, which allows remote authenticated users to
SimStudio below 0.5.74 has a missing authorization on MongoDB tool endpoints that allows attackers to execute arbitrary
MongoDB Server may access non-initialized region of memory leading to unexpected behaviour when zero arguments are calle
MongoDB Compass may be susceptible to code injection due to insufficient sandbox protection settings with the usage of e
Under certain configurations of --tlsCAFile and tls.CAFile, MongoDB Server may skip peer certificate validation which ma
All versions of bson before 1.1.4 are vulnerable to Deserialization of Untrusted Data. Rated critical severity (CVSS 9.8
Memory corruption in the MongoDB BI Connector ODBC Driver (fixed in v1.4.9) occurs when an oversized catalog, schema, or
EUVD-2026-67214
NVD
CVE.org
EPSS
Vulnrichment
VulDB
GitHub PoC
Exploit-DB