CVE-2026-18687

HIGHPre-NVD 7.17.1—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.1EG
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.1Exploit: None knownExposed: 0

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

MongoDB Server's handling of a Queryable Encryption maintenance operation did not properly validate certain request parameters against the collection's encrypted field configuration before use. An authenticated user with readWrite privileges could submit a specially formed request that leads to a server crash or excessive internal writes, resulting in resource exhaustion and corruption of encrypted index data.

CVSS v3
7.1
EG Score
7.1(high)
EG Risk
32(Track)
EG Risk 32/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
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
7%
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-130628

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-18687?
CVE-2026-18687 is a high vulnerability published on August 11, 2026. MongoDB Server's handling of a Queryable Encryption maintenance operation did not properly validate certain request parameters against the collection's encrypted field configuration before use. An authenticated user with readWrite privileges could submit a specially formed request that leads to a…
When was CVE-2026-18687 disclosed?
CVE-2026-18687 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-18687 actively exploited?
CVE-2026-18687 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 93.5% of all scored CVEs.
What is the CVSS score of CVE-2026-18687?
CVE-2026-18687 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-18687?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-18687, 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-18687

Explore →

Is Your Infrastructure Affected by CVE-2026-18687?

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

Start Free Scan →Browse All CVEs