CVE-2026-18710

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1% (3rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
6.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 6.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.5MEDIUMmedium confidence
EG Risk
29
EG Risk 29/100

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 (value × EchelonGraph’s weight)
Severity65% × 45%
The EG Score, 6.5 of 10.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
3rd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 11, 2026

Last Modified

September 25, 2026

Advisory Details (1)

Auto-updated Aug 11, 2026
Patch available.
Web page

Loading...

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

Vendor Advisories for CVE-2026-18710(3)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatmongodb-driver-legacy2026-09-03redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 40× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 111 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 11 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  2. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  3. 2026-10-12 16:27 UTCEG score recompute
  4. 2026-10-11 20:07 UTCEG score recompute
  5. 2026-10-11 17:20 UTCEG score recompute
  6. 2026-10-11 14:52 UTCEG score recompute
  7. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  8. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  9. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  10. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  11. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  12. 2026-10-06 18:43 UTCEG score recompute
  13. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  14. 2026-10-05 20:39 UTCEG score recompute
  15. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  16. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  17. 2026-10-03 20:26 UTCEG score recompute
  18. 2026-10-02 08:25 UTCEG score recompute
  19. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  20. 2026-09-30 22:00 UTCEG score recompute
  21. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  22. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  23. 2026-09-29 06:17 UTCEG score recompute
  24. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  25. 2026-09-28 08:11 UTCEG score recompute
Show 75 more
  1. 2026-09-27 13:47 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  2. 2026-09-27 09:59 UTCEG score recompute
  3. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  4. 2026-09-25 03:44 UTCEG score recompute
  5. 2026-09-23 20:57 UTCEG score recompute
  6. 2026-09-22 21:08 UTCEG score recompute
  7. 2026-09-21 20:15 UTCEG score recompute
  8. 2026-09-19 20:45 UTCEG score recompute
  9. 2026-09-18 22:38 UTCEG score recompute
  10. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  11. 2026-09-18 00:34 UTCEG score recompute
  12. 2026-09-17 00:25 UTCEG score recompute
  13. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  14. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  15. 2026-09-15 22:08 UTCEG score recompute
  16. 2026-09-13 20:08 UTCEG score recompute
  17. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  18. 2026-09-12 22:03 UTCEG score recompute
  19. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  20. 2026-09-11 23:57 UTCEG score recompute
  21. 2026-09-11 23:57 UTCVendor advisory
  22. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  23. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  24. 2026-09-11 01:32 UTCEG score recompute
  25. 2026-09-11 01:32 UTCVendor advisory
  26. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  27. 2026-09-10 03:26 UTCVendor advisory
  28. 2026-09-09 05:21 UTCEG score recompute
  29. 2026-09-09 05:21 UTCVendor advisory
  30. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  31. 2026-09-07 19:05 UTCEG score recompute
  32. 2026-09-07 19:05 UTCVendor advisory
  33. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  34. 2026-09-06 21:00 UTCEG score recompute
  35. 2026-09-06 21:00 UTCVendor advisory
  36. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  37. 2026-09-05 22:54 UTCVendor advisory
  38. 2026-09-05 00:49 UTCEG score recompute
  39. 2026-09-05 00:49 UTCVendor advisory
  40. 2026-09-04 01:40 UTCVendor advisory
  41. 2026-09-02 23:43 UTCEG score recompute
  42. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  43. 2026-09-01 20:26 UTCEG score recompute
  44. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  45. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  46. 2026-08-31 21:44 UTCEG score recompute
  47. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  48. 2026-08-30 18:52 UTCEG score recompute
  49. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  50. 2026-08-28 21:49 UTCEG score recompute
  51. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  52. 2026-08-28 05:53 UTCEG score recompute
  53. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  54. 2026-08-27 07:24 UTCEG score recompute
  55. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  56. 2026-08-26 08:59 UTCEG score recompute
  57. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  58. 2026-08-25 10:54 UTCEG score recompute
  59. 2026-08-24 12:49 UTCEG score recompute
  60. 2026-08-23 14:44 UTCEG score recompute
  61. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  62. 2026-08-22 16:39 UTCEG score recompute
  63. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  64. 2026-08-21 18:34 UTCEG score recompute
  65. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  66. 2026-08-19 22:24 UTCEG score recompute
  67. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  68. 2026-08-19 00:17 UTCEG score recompute
  69. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  70. 2026-08-18 02:11 UTCEG score recompute
  71. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  72. 2026-08-17 04:03 UTCEG score recompute
  73. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  74. 2026-08-16 05:57 UTCEG score recompute
  75. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.1% · 1st percentile

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-18710?
CVE-2026-18710 is a medium-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-18710 published?
The CVE record for CVE-2026-18710 was published on August 11, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 25, 2026; the record at its source may have been updated since.
Is CVE-2026-18710 actively exploited?
CVE-2026-18710 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (3rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-18710?
CVE-2026-18710 has a CVSS base score of 6.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-18710?
A fix for CVE-2026-18710 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-18710 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs