CVE-2026-9735

MEDIUMPre-NVD 5.55.5—
EchelonGraph scoreHIGH confidence

Score 5.5 from GitHub Security Advisory published 2026-06-10. a secondary CVSS source baseline 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
5.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

MongoDB 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.

CVSS v3
5.5
EG Score
5.5(high)
EPSS
2.1%
KEV
Not listed

Published

June 9, 2026

Last Modified

June 15, 2026

Advisory Details (1)

Auto-updated Jun 13, 2026
No patch confirmed yet.
generic

Loading...

https://jira.mongodb.org/browse/SERVER-126506

Vendor Advisories for CVE-2026-9735(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 17× in last 7d / 80× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 16:27 UTCEPSS rescore
  2. 2026-07-06 02:23 UTCEPSS rescore
  3. 2026-07-05 12:00 UTCEG score recompute
  4. 2026-07-05 12:00 UTCGHSA enrichment
  5. 2026-07-04 12:50 UTCEG score recompute
  6. 2026-07-04 12:50 UTCGHSA enrichment
  7. 2026-07-04 06:31 UTCEPSS rescore
  8. 2026-07-03 08:36 UTCEG score recompute
  9. 2026-07-03 08:36 UTCGHSA enrichment
  10. 2026-07-02 07:19 UTCEG score recompute
  11. 2026-07-02 07:19 UTCGHSA enrichment
  12. 2026-07-01 15:07 UTCEPSS rescore
  13. 2026-07-01 08:02 UTCEG score recompute
  14. 2026-07-01 08:02 UTCGHSA enrichment
  15. 2026-06-30 23:22 UTCEPSS rescore
  16. 2026-06-30 08:55 UTCEG score recompute
  17. 2026-06-30 08:55 UTCGHSA enrichment
  18. 2026-06-29 14:06 UTCEPSS rescore
  19. 2026-06-29 09:49 UTCEG score recompute
  20. 2026-06-29 09:49 UTCGHSA enrichment
  21. 2026-06-28 14:07 UTCEPSS rescore
  22. 2026-06-28 10:42 UTCEG score recompute
  23. 2026-06-28 10:42 UTCGHSA enrichment
  24. 2026-06-28 04:56 UTCEPSS rescore
  25. 2026-06-27 11:36 UTCEG score recompute
Show 55 more
  1. 2026-06-27 11:36 UTCGHSA enrichment
  2. 2026-06-27 03:08 UTCEPSS rescore
  3. 2026-06-26 12:27 UTCEG score recompute
  4. 2026-06-26 12:26 UTCGHSA enrichment
  5. 2026-06-25 13:50 UTCEPSS rescore
  6. 2026-06-25 12:41 UTCEG score recompute
  7. 2026-06-25 12:41 UTCGHSA enrichment
  8. 2026-06-24 14:05 UTCEPSS rescore
  9. 2026-06-24 13:35 UTCEG score recompute
  10. 2026-06-24 13:35 UTCGHSA enrichment
  11. 2026-06-23 21:33 UTCEPSS rescore
  12. 2026-06-23 13:10 UTCEG score recompute
  13. 2026-06-23 13:09 UTCGHSA enrichment
  14. 2026-06-22 14:25 UTCEPSS rescore
  15. 2026-06-22 13:36 UTCEG score recompute
  16. 2026-06-22 13:35 UTCGHSA enrichment
  17. 2026-06-21 14:56 UTCEPSS rescore
  18. 2026-06-21 14:23 UTCEG score recompute
  19. 2026-06-21 14:22 UTCGHSA enrichment
  20. 2026-06-21 01:59 UTCEPSS rescore
  21. 2026-06-20 14:26 UTCEG score recompute
  22. 2026-06-20 14:26 UTCGHSA enrichment
  23. 2026-06-19 19:26 UTCEPSS rescore
  24. 2026-06-19 15:19 UTCEG score recompute
  25. 2026-06-19 15:19 UTCGHSA enrichment
  26. 2026-06-18 17:52 UTCEPSS rescore
  27. 2026-06-18 16:13 UTCEG score recompute
  28. 2026-06-18 16:12 UTCGHSA enrichment
  29. 2026-06-17 17:53 UTCEPSS rescore
  30. 2026-06-17 17:06 UTCEG score recompute
  31. 2026-06-17 17:06 UTCGHSA enrichment
  32. 2026-06-16 17:53 UTCEPSS rescore
  33. 2026-06-16 17:18 UTCEG score recompute
  34. 2026-06-16 17:18 UTCGHSA enrichment
  35. 2026-06-15 18:11 UTCEG score recompute
  36. 2026-06-15 18:11 UTCGHSA enrichment
  37. 2026-06-15 17:49 UTCEPSS rescore
  38. 2026-06-14 23:18 UTCEPSS rescore
  39. 2026-06-14 18:53 UTCEG score recompute
  40. 2026-06-14 18:53 UTCGHSA enrichment
  41. 2026-06-13 23:00 UTCEPSS rescore
  42. 2026-06-13 19:47 UTCEG score recompute
  43. 2026-06-13 19:46 UTCGHSA enrichment
  44. 2026-06-12 23:12 UTCEPSS rescore
  45. 2026-06-12 23:12 UTCEPSS rescore
  46. 2026-06-12 20:37 UTCEG score recompute
  47. 2026-06-12 20:36 UTCGHSA enrichment
  48. 2026-06-11 21:30 UTCEG score recompute
  49. 2026-06-11 21:30 UTCGHSA enrichment
  50. 2026-06-11 14:00 UTCEPSS rescore
  51. 2026-06-10 22:23 UTCEG score recompute
  52. 2026-06-10 22:23 UTCGHSA enrichment
  53. 2026-06-10 22:19 UTCEPSS rescore
  54. 2026-06-09 23:17 UTCEG score recompute
  55. 2026-06-09 23:17 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-9735?
CVE-2026-9735 is a medium vulnerability published on June 9, 2026. MongoDB 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.
When was CVE-2026-9735 disclosed?
CVE-2026-9735 was first published in the National Vulnerability Database on June 9, 2026, with the most recent update on June 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-9735 actively exploited?
CVE-2026-9735 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-9735?
CVE-2026-9735 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-9735?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-9735, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-9735

Explore →

Is Your Infrastructure Affected by CVE-2026-9735?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs