Analyst readout for executives and security teams
Plain-English summary
MongoDB Server may write an LDAP query password in plain text to mongod.log when ldapQueryPassword is changed using the runtime setParameter command. This is mainly a credential exposure issue: anyone who can read the database logs could recover that password. The CVE is medium severity and is not listed as actively exploited in the provided sources.
Executive priority
Treat this as a credential exposure cleanup and configuration-risk issue. Prioritize environments using MongoDB LDAP integration, especially where logs are broadly accessible or forwarded to shared platforms. Rotate exposed credentials promptly if evidence shows the password entered logs.
Technical view
CVE-2026-9751 is CWE-532: insertion of sensitive information into a log file. The issue affects MongoDB Server versions 8.3.0, 8.2.0, 8.0.0, and 7.0.0 per the source bundle. Attack requirements are local access and low privileges, with high confidentiality impact and no integrity or availability impact in the CVSS v4.0 vector.
Likely exposure
Exposure is likely limited to deployments using MongoDB LDAP configuration where ldapQueryPassword is modified through runtime setParameter. Risk depends on who can read mongod.log, centralized log stores, backups, and support bundles containing those logs.
Exploitation context
The provided sources do not report active exploitation or KEV listing. Exploitation would primarily involve unauthorized or overly broad access to MongoDB log files after the password has been logged. The issue does not describe remote code execution or service disruption.
Researcher notes
Evidence is limited to the CVE record, CVE List entry, and MongoDB Jira reference. The bundle does not name a patched version or detailed workaround. The core trigger is specific: setting ldapQueryPassword via runtime setParameter causes the new password to be logged in plain text.
Mitigation direction
- Check MongoDB’s SERVER-123370 guidance for fixed versions or vendor-recommended handling.
- Avoid changing ldapQueryPassword through runtime setParameter until vendor guidance is applied.
- Restrict access to mongod.log and any centralized copies containing MongoDB logs.
- Rotate the LDAP password if it may have been logged in plain text.
- Review log retention, backups, and support bundles for exposed credentials.
Validation and detection
- Identify MongoDB Server instances running affected versions listed in the CVE.
- Determine whether ldapQueryPassword was changed through runtime setParameter.
- Inspect mongod.log and log aggregation systems for exposed LDAP password values.
- Verify permissions on MongoDB logs and downstream log storage.
- Confirm whether vendor guidance or an updated release has been applied.
Public sources used
Based on public source material and reviewed before publication.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-532: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-9751 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.8 (4.0)
- Known Exploited
- No
- Published
Vector: 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
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
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 — — mongodb CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N 1.8 3.6 mongodb Vulnerability scoring details
Base CVSS 4.0 score
6.8 MediumVector: 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
Base CVSS 3.1 score
5.5 MediumVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reserved CVE Program
The CVE ID was reserved by the assigning CNA.
- CVE published CVE Program
The CVE record was published.
- CVE updated CVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 source CVE List V5
- https://jira.mongodb.org/browse/SERVER-123370 CVE reference, mongodb
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Insertion of Sensitive Information into Log File
Insertion of Sensitive Information into Log File represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.