dbcve.org
MongoDBDatabase / datastore

CVE-2026-9751

MEDIUM · 5.5 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to 7.0.35 / 8.0.24 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The ldapQueryPassword parameter, when set through the runtime setParameter command, will log the new password to the mongod.log file in plain text.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

When the ldapQueryPassword parameter is set at runtime using the setParameter command in MongoDB, the plain text password is written to the mongod.log file, exposing LDAP credentials to anyone with log file access.

MitigationAvoid using runtime setParameter for ldapQueryPassword; configure LDAP passwords via configuration files instead. Implement strict access controls on log directories and consider log rotation/cleanup policies.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MongoDBDatabase / datastore
Affected:>= 7.0.0, < 7.0.35>= 8.0.0, < 8.0.24>= 8.2.0, < 8.2.10>= 8.3.0, < 8.3.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check MongoDB server version
    Run 'db.version()' in mongosh or execute 'mongod --version' to obtain the installed version number
    Affected if The version falls within >= 7.0.0, < 7.0.35; >= 8.0.0, < 8.0.24; >= 8.2.0, < 8.2.10; or >= 8.3.0, < 8.3.3
  2. Determine if LDAP authentication is configured
    Check MongoDB configuration for LDAP-related settings, particularly ldapQueryUser and ldapQueryPassword parameters in the configuration file or via 'db.adminCommand({getParameter: 1, ldapQueryPassword: 1})'
    Affected if LDAP authentication is enabled and ldapQueryPassword is set
  3. Inspect mongod.log for plaintext passwords
    Search the mongod.log file for the literal string 'ldapQueryPassword' or any plain text passwords that appear near LDAP configuration entries
    Affected if Plaintext ldapQueryPassword values are visible in the log file
  4. Check if ldapQueryPassword was set via runtime setParameter
    Review command history, automation scripts, or mongod logs for entries containing 'setParameter' and 'ldapQueryPassword' to determine if the runtime command was used
    Affected if The ldapQueryPassword parameter was modified using the runtime setParameter command

A user is affected if their MongoDB version is within the affected ranges, LDAP authentication is configured with ldapQueryPassword set via runtime setParameter, and plaintext credentials appear in mongod.log

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 7.0.35 / 8.0.24 / 8.2.10 or later
Fixed in 7.0.358.0.248.2.10
Interim mitigation

Avoid using runtime setParameter for ldapQueryPassword; configure LDAP passwords via configuration files instead. Implement strict access controls on log directories and consider log rotation/cleanup policies.

Recommended fix High confidence

7.0.35 / 8.0.24 / 8.2.10 / 8.3.3 (depending on your major version branch)

  1. 1. Backup your MongoDB database and configuration files before proceeding with the upgrade.
  2. 2. Schedule a maintenance window as the upgrade may require service restart.
  3. 3. For MongoDB 7.0.x: Upgrade to version 7.0.35 or later.
  4. 4. For MongoDB 8.0.x: Upgrade to version 8.0.24 or later.
  5. 5. For MongoDB 8.2.x: Upgrade to version 8.2.10 or later.
  6. 6. For MongoDB 8.3.x: Upgrade to version 8.3.3 or later.
  7. 7. After upgrade, verify that ldapQueryPassword is no longer logged in plain text by reviewing mongod.log entries.
  8. 8. Consider using configuration file or environment variables instead of runtime setParameter for ldapQueryPassword to avoid storing sensitive values in memory.
Caveat Standard MongoDB upgrade considerations apply; review release notes for any configuration or feature changes between your current version and the target version.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in MongoDB Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-9751 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-9751 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data