CVE-2026-18693

HIGHPre-NVD 7.67.6—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.6EG
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.6Exploit: 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 handling of timeseries collections could allow an authenticated user with write privileges to cause an internal data structure to become inconsistent through certain document insertions. A subsequent insert into the affected bucket could then result in the server accessing memory outside its intended bounds, potentially causing a server crash (denial of service), exposure of limited memory contents, or memory corruption.

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

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-18693?
CVE-2026-18693 is a high vulnerability published on August 11, 2026. An issue in MongoDB Server's handling of timeseries collections could allow an authenticated user with write privileges to cause an internal data structure to become inconsistent through certain document insertions. A subsequent insert into the affected bucket could then result in the server…
When was CVE-2026-18693 disclosed?
CVE-2026-18693 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-18693 actively exploited?
CVE-2026-18693 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 86.1% of all scored CVEs.
What is the CVSS score of CVE-2026-18693?
CVE-2026-18693 has a CVSS v3 base score of 7.6 (NVD).
How do I remediate CVE-2026-18693?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-18693, 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-18693

Explore →

Is Your Infrastructure Affected by CVE-2026-18693?

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

Start Free Scan →Browse All CVEs