Skip to main content

MongoDB Server CVE-2026-9735

| EUVDEUVD-2026-35856 MEDIUM
Insertion of Sensitive Information into Log File (CWE-532)
2026-06-09 mongodb GHSA-93h4-p6c6-58pw
6.8
CVSS 4.0 · Vendor: mongodb
Share

Severity by source

Vendor (mongodb) PRIMARY
6.8 MEDIUM
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Primary rating from Vendor (mongodb) · only source for this CVE.

CVSS VectorVendor: mongodb

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
X

Lifecycle Timeline

3
Patch available
Jun 10, 2026 - 02:01 EUVD
Analysis Generated
Jun 09, 2026 - 23:23 vuln.today
CVSS changed
Jun 09, 2026 - 23:22 NVD
5.5 (MEDIUM) 6.8 (MEDIUM)

DescriptionCVE.org

MongoDB server may log authentication parameters, including credentials, to the server log during SASL authentication. When connection health metric logging is enabled, the full authentication parameters are written to the log without redaction.

AnalysisAI

MongoDB Server leaks SASL authentication credentials into plaintext server logs when connection health metric logging is enabled, exposing database passwords to any local actor with log file read access. The flaw (CWE-532) affects all versions per the available CPE data and was self-disclosed by MongoDB, indicating a vendor-acknowledged issue without a confirmed patch version at time of analysis. A low-privileged local attacker who can read the MongoDB log directory can harvest credentials and authenticate directly to the database - no public exploit exists at time of analysis, and it is not listed in the CISA KEV catalog.

Technical ContextAI

The root cause is CWE-532 (Insertion of Sensitive Information into Log File), a class of vulnerability where the application writes security-sensitive data to diagnostic output without sanitization. SASL (Simple Authentication and Security Layer) is the authentication framework MongoDB uses for mechanisms such as SCRAM-SHA-1, SCRAM-SHA-256, GSSAPI, and PLAIN. During SASL authentication, the server exchanges structured parameter payloads that include credential material. MongoDB's connection health metric logging subsystem - when enabled - captures the full authentication parameter object and writes it verbatim to the server log, bypassing any credential redaction logic applied in other log paths. The CPE string cpe:2.3:a:mongodb:mongodb_server:*:*:*:*:*:*:*:* with an unrestricted version wildcard indicates MongoDB has not yet scoped the issue to a specific version range, suggesting broad exposure across the product line. The CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:L) confirms the attack surface is limited to the local system filesystem rather than the network layer.

RemediationAI

No vendor-released patched version has been independently confirmed - the only available reference is MongoDB Jira ticket SERVER-126506 (https://jira.mongodb.org/browse/SERVER-126506), which should be monitored for patch release details and an official advisory with exact fix versions. As an immediate compensating control, disable connection health metric logging if it is not operationally required; this directly eliminates the code path responsible for unredacted credential writes and carries no functional impact for workloads that do not depend on this diagnostic feature. If health metric logging must remain enabled for operational reasons, restrict filesystem read permissions on MongoDB log directories to only trusted administrative accounts and service identities, removing access for application-tier or lower-privilege OS accounts. Additionally, conduct a retrospective review of existing log files for exposed credential material and rotate any SASL credentials (usernames and passwords) that may have been written to logs while the feature was active. Until an official patch is available, treat log file access control as a primary security boundary for this deployment.

CVE-2013-1892 MEDIUM POC
6.0 Oct 01

MongoDB before 2.0.9 and 2.2.x before 2.2.4 does not properly validate requests to the nativeHelper function in SpiderMo

CVE-2013-3969 MEDIUM POC
6.5 Oct 01

The find prototype in scripting/engine_v8.h in MongoDB 2.4.0 through 2.4.4 allows remote authenticated users to cause a

CVE-2018-13863 HIGH POC
7.5 Jul 10

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

CVE-2026-25887 HIGH POC
7.2 Mar 06

Remote code execution in Chartbrew versions prior to 4.8.1 allows authenticated attackers with high privileges to execut

CVE-2019-2386 HIGH POC
7.1 Aug 06

After user deletion in MongoDB Server the improper invalidation of authorization sessions allows an authenticated user's

CVE-2012-6619 MEDIUM POC
6.4 Mar 06

The default configuration for MongoDB before 2.3.2 does not validate objects, which allows remote authenticated users to

CVE-2026-3431 CRITICAL
9.8 Mar 02

SimStudio below 0.5.74 has a missing authorization on MongoDB tool endpoints that allows attackers to execute arbitrary

CVE-2024-8654 CRITICAL
9.8 Sep 10

MongoDB Server may access non-initialized region of memory leading to unexpected behaviour when zero arguments are calle

CVE-2024-6376 CRITICAL
9.8 Jul 01

MongoDB Compass may be susceptible to code injection due to insufficient sandbox protection settings with the usage of e

CVE-2024-1351 CRITICAL
9.8 Mar 07

Under certain configurations of --tlsCAFile and tls.CAFile, MongoDB Server may skip peer certificate validation which ma

CVE-2020-7610 CRITICAL
9.8 Mar 30

All versions of bson before 1.1.4 are vulnerable to Deserialization of Untrusted Data. Rated critical severity (CVSS 9.8

CVE-2026-19001 CRITICAL
9.5 Aug 12

Memory corruption in the MongoDB BI Connector ODBC Driver (fixed in v1.4.9) occurs when an oversized catalog, schema, or

Share

CVE-2026-9735 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy