CVE-2026-18697

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-11. a secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: 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's aggregation framework could allow an unauthenticated party to cause a mongos (router) process to terminate unexpectedly by submitting a specially formed aggregation command. This could result in a denial of service, disrupting client connections routed through the affected mongos instance.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
49(Track)
EG Risk 49/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
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
25%
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-130110

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-18697?
CVE-2026-18697 is a high vulnerability published on August 11, 2026. An issue in MongoDB Server's aggregation framework could allow an unauthenticated party to cause a mongos (router) process to terminate unexpectedly by submitting a specially formed aggregation command. This could result in a denial of service, disrupting client connections routed through the…
When was CVE-2026-18697 disclosed?
CVE-2026-18697 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-18697 actively exploited?
CVE-2026-18697 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 74.7% of all scored CVEs.
What is the CVSS score of CVE-2026-18697?
CVE-2026-18697 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-18697?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-18697, 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-18697

Explore →

Is Your Infrastructure Affected by CVE-2026-18697?

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

Start Free Scan →Browse All CVEs