CVE-2026-18709

MEDIUMPre-NVD 6.46.4—
EchelonGraph scoreHIGH confidence

Score 6.4 from GitHub Security Advisory published 2026-08-11. a secondary CVSS source baseline 6.4; sources differ by 0.0.

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

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

An issue in MongoDB Server could allow an authenticated user with direct network access to a shard to improperly commit or abort an in-progress prepared transaction, bypassing the intended transaction coordination process. This could result in cross-shard data inconsistency, cluster clock corruption, and violation of transaction atomicity guarantees.

CVSS v3
6.4
EG Score
6.4(high)
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
Severity64% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
4%
KEV
Not listed

Published

August 11, 2026

Last Modified

August 11, 2026

Advisory Details (1)

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

Loading...

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

Vendor Advisories for CVE-2026-18709(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 23× in last 7d / 33× 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-21 03:35 UTCEG score recompute
  2. 2026-08-21 03:35 UTCGHSA enrichment
  3. 2026-08-20 22:55 UTCEPSS rescore
  4. 2026-08-20 05:22 UTCEG score recompute
  5. 2026-08-20 05:22 UTCGHSA enrichment
  6. 2026-08-19 17:03 UTCEPSS rescore
  7. 2026-08-19 07:08 UTCEG score recompute
  8. 2026-08-19 07:08 UTCGHSA enrichment
  9. 2026-08-18 13:48 UTCEPSS rescore
  10. 2026-08-18 08:54 UTCEG score recompute
  11. 2026-08-18 08:53 UTCGHSA enrichment
  12. 2026-08-17 13:47 UTCEPSS rescore
  13. 2026-08-17 10:39 UTCEG score recompute
  14. 2026-08-17 10:39 UTCGHSA enrichment
  15. 2026-08-16 14:56 UTCEPSS rescore
  16. 2026-08-16 12:26 UTCEG score recompute
  17. 2026-08-16 12:26 UTCGHSA enrichment
  18. 2026-08-16 02:14 UTCEPSS rescore
  19. 2026-08-15 14:13 UTCEG score recompute
  20. 2026-08-15 14:13 UTCGHSA enrichment
  21. 2026-08-15 01:30 UTCEPSS rescore
  22. 2026-08-14 15:59 UTCEG score recompute
  23. 2026-08-14 15:59 UTCGHSA enrichment
  24. 2026-08-13 22:00 UTCEPSS rescore
  25. 2026-08-13 17:45 UTCGHSA enrichment
Show 8 more
  1. 2026-08-12 19:31 UTCEG score recompute
  2. 2026-08-12 19:31 UTCGHSA enrichment
  3. 2026-08-12 13:50 UTCEPSS rescore
  4. 2026-08-11 21:18 UTCEG score recompute
  5. 2026-08-11 20:31 UTCEG score recompute
  6. 2026-08-11 19:18 UTCEG score recompute
  7. 2026-08-11 19:01 UTCEG score recompute
  8. 2026-08-11 19:01 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-18709?
CVE-2026-18709 is a medium vulnerability published on August 11, 2026. An issue in MongoDB Server could allow an authenticated user with direct network access to a shard to improperly commit or abort an in-progress prepared transaction, bypassing the intended transaction coordination process. This could result in cross-shard data inconsistency, cluster clock…
When was CVE-2026-18709 disclosed?
CVE-2026-18709 was first published in the National Vulnerability Database on August 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-18709 actively exploited?
CVE-2026-18709 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 96.1% of all scored CVEs.
What is the CVSS score of CVE-2026-18709?
CVE-2026-18709 has a CVSS v3 base score of 6.4 (NVD).
How do I remediate CVE-2026-18709?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-18709, 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-18709

Explore →

Is Your Infrastructure Affected by CVE-2026-18709?

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

Start Free Scan →Browse All CVEs