Credential disclosure via unredacted SASL parameter logging
Published Jun 9, 2026 · Updated Jun 9, 2026
Sensitive-data logging in MongoDB Server 8.3.0 through 8.3.2 allows local users to read SASL authentication credentials from server logs. The connection-health authentication metrics path writes full SASL authentication parameters to the server log without applying credential redaction. Exposure requires connection-health metric logging, which defaults to enabled, and access to the resulting server log.
Summary
What happened
Sensitive-data logging in MongoDB Server 8.3.0 through 8.3.2 allows local users to read SASL authentication credentials from server logs. The connection-health authentication metrics path writes full SASL authentication parameters to the server log without applying credential redaction. Exposure requires connection-health metric logging, which defaults to enabled, and access to the resulting server log.
The record
- CVE
- CVE-2026-9735
- Published
- Jun 9, 2026
- Updated
- Jun 9, 2026
- Vendor
- MongoDB
- Product
- MongoDB Server
- Classifications
- CWE-532, T1552.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 9, 2026CVE publishedPublication date reported by the CVE source.
- Jun 9, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=8.3.0 <8.3.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo