Analyst readout for executives and security teams
Plain-English summary
MongoDB Server 8.3.0 can write sensitive authentication details, including credentials or keyfile contents, into server logs during SASL authentication when connection health metric logging is enabled. This is mainly a credential exposure risk through log access rather than remote code execution.
Executive priority
Treat as a moderate priority, elevated where MongoDB logs are broadly accessible or exported. The business risk is credential disclosure from logs, which can lead to unauthorized database access if exposed secrets remain valid.
Technical view
CVE-2026-9735 is a CWE-532 information exposure flaw in MongoDB Server 8.3.0. With connection health metric logging enabled, SASL authentication parameters are logged without redaction. CVSS 4.0 is 6.8 with local attack vector and low privileges, and confidentiality impact is high.
Likely exposure
Exposure is likely limited to MongoDB Server 8.3.0 deployments using SASL authentication with connection health metric logging enabled, especially where logs are exported to shared SIEM, support bundles, backups, or broad operations tooling.
Exploitation context
The source bundle does not report active exploitation, and the CVE is not listed as KEV. Abuse would require access to affected server logs or systems receiving those logs, then use of exposed authentication material.
Researcher notes
Evidence is limited to the CVE bundle and MongoDB Jira reference. Sources identify the affected version and logging condition but do not provide a named patch version, exploit activity, or detailed vendor remediation in the supplied material.
Mitigation direction
- Check MongoDB vendor guidance for fixed versions or official workarounds.
- Disable connection health metric logging where operationally acceptable.
- Restrict access to MongoDB server logs and centralized log stores.
- Rotate credentials or keyfiles if logs may contain exposed authentication material.
- Purge or secure affected historical logs according to retention requirements.
Validation and detection
- Inventory MongoDB Server deployments and identify version 8.3.0 instances.
- Confirm whether connection health metric logging is enabled.
- Review SASL authentication logging paths with restricted, authorized access.
- Check centralized logging, backups, and support archives for exposed authentication parameters.
- Track the MongoDB Jira issue and CVE record for remediation updates.
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 lookupCVE-2026-9735 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-126506 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.