CVE-2026-18710

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 98% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: None knownExposed: 0

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

A MongoDB driver component could write sensitive configuration information, including a credential used for outbound network connectivity, to application log output in cleartext during routine client initialization. This occurs automatically as part of normal operation and requires no special privileges to trigger. A party able to read the affected application's logs or downstream log-aggregation storage could recover the credential and reuse it to authenticate to the associated network infrastructure. This issue affects confidentiality only.

CVSS v3
6.5
EG Score
6.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity65% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

August 11, 2026

Last Modified

August 12, 2026

Advisory Details (1)

Auto-updated Aug 11, 2026
No patch confirmed yet.
generic

Loading...

https://jira.mongodb.org/browse/JAVA-6266

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 34× 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-08-27 14:25 UTCEPSS rescore
  2. 2026-08-27 07:24 UTCEG score recompute
  3. 2026-08-26 14:46 UTCEPSS rescore
  4. 2026-08-26 08:59 UTCEG score recompute
  5. 2026-08-25 13:48 UTCEPSS rescore
  6. 2026-08-25 10:54 UTCEG score recompute
  7. 2026-08-24 12:49 UTCEG score recompute
  8. 2026-08-23 14:44 UTCEG score recompute
  9. 2026-08-23 00:19 UTCEPSS rescore
  10. 2026-08-22 16:39 UTCEG score recompute
  11. 2026-08-21 23:49 UTCEPSS rescore
  12. 2026-08-21 18:34 UTCEG score recompute
  13. 2026-08-20 22:55 UTCEPSS rescore
  14. 2026-08-19 22:24 UTCEG score recompute
  15. 2026-08-19 17:03 UTCEPSS rescore
  16. 2026-08-19 00:17 UTCEG score recompute
  17. 2026-08-18 13:48 UTCEPSS rescore
  18. 2026-08-18 02:11 UTCEG score recompute
  19. 2026-08-17 13:47 UTCEPSS rescore
  20. 2026-08-17 04:03 UTCEG score recompute
  21. 2026-08-16 14:56 UTCEPSS rescore
  22. 2026-08-16 05:57 UTCEG score recompute
  23. 2026-08-16 02:14 UTCEPSS rescore
  24. 2026-08-15 07:53 UTCEG score recompute
  25. 2026-08-15 01:30 UTCEPSS rescore
Show 9 more
  1. 2026-08-14 09:48 UTCEG score recompute
  2. 2026-08-13 22:00 UTCEPSS rescore
  3. 2026-08-13 11:43 UTCEG score recompute
  4. 2026-08-12 13:50 UTCEPSS rescore
  5. 2026-08-12 13:38 UTCEG score recompute
  6. 2026-08-12 12:55 UTCEG score recompute
  7. 2026-08-11 22:18 UTCEG score recompute
  8. 2026-08-11 22:06 UTCEG score recompute
  9. 2026-08-11 22:05 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-18710?
CVE-2026-18710 is a medium vulnerability published on August 11, 2026. A MongoDB driver component could write sensitive configuration information, including a credential used for outbound network connectivity, to application log output in cleartext during routine client initialization. This occurs automatically as part of normal operation and requires no special…
When was CVE-2026-18710 disclosed?
CVE-2026-18710 was first published in the National Vulnerability Database on August 11, 2026, with the most recent update on August 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-18710 actively exploited?
CVE-2026-18710 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.8% of all scored CVEs.
What is the CVSS score of CVE-2026-18710?
CVE-2026-18710 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-18710?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-18710, 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-18710

Explore →

Is Your Infrastructure Affected by CVE-2026-18710?

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

Start Free Scan →Browse All CVEs