MongoDBDatabase / datastore
CVE-2026-9735
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 · uneditedMongoDB 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.
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 · high confidenceMongoDB server logs SASL authentication parameters, including plaintext credentials, to server logs without redaction when connection health metric logging is enabled, leading to credential exposure in server log files.
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
>= 8.3.0, < 8.3.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check MongoDB server versionRun `db.adminCommand({getParameter:1, version:1})` in the mongo shell, or check the version string in the server log header, or run `mongod --version`Affected if version is >= 8.3.0 and < 8.3.3
-
Verify connection health metric logging is enabledInspect the MongoDB configuration file (typically mongod.conf) or runtime configuration for any setting that enables connection health metric logging or diagnostics. Check for parameters related to connection health monitoring or diagnostic data collection.Affected if connection health metric logging is explicitly turned on in the configuration
-
Examine recent server logs for exposed credentialsSearch the MongoDB server log files (default path /var/log/mongodb/ on Linux) for entries during SASL authentication that contain authentication parameters. Look for plaintext username or password strings appearing in log lines related to connection health or SASL auth.Affected if log entries contain plaintext credentials during SASL authentication with connection health logging active
The environment is affected if the installed MongoDB version falls within 8.3.0 to 8.3.3 AND connection health metric logging is enabled, resulting in plaintext credentials appearing in server logs.
Generated from the published advisory. Verify against your own configuration.
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 · scoped8.3.3
Disable or reconfigure connection health metric logging in MongoDB configuration to prevent credential leakage, and rotate any credentials that may have been exposed in logs.
8.3.3
- Upgrade MongoDB server to version 8.3.3 or later to resolve the credential logging vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in MongoDB
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-9735 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-9735 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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