CVE-2026-82068

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreHIGH confidence

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

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

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

A security issue in MongoDB Server allows an authenticated user with write privileges to trigger a persistent fatal assertion crash by sending specially crafted retryable write commands. The crash state is durably persisted, causing the server process to repeatedly crash on restart and potentially propagating to additional nodes in a sharded cluster. Manual intervention is required to restore service availability.

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

Published

September 8, 2026

Last Modified

September 16, 2026

Advisory Details (1)

Auto-updated Sep 8, 2026
No patch confirmed yet.
generic

Loading...

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

Vendor Advisories for CVE-2026-82068(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 20× 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-09-19 17:21 UTCEG score recompute
  2. 2026-09-19 17:21 UTCGHSA enrichment
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 18:50 UTCGHSA enrichment
  5. 2026-09-17 20:19 UTCEG score recompute
  6. 2026-09-17 20:19 UTCGHSA enrichment
  7. 2026-09-16 21:09 UTCEG score recompute
  8. 2026-09-16 21:09 UTCGHSA enrichment
  9. 2026-09-16 14:08 UTCEPSS rescore
  10. 2026-09-16 08:57 UTCEG score recompute
  11. 2026-09-16 08:57 UTCGHSA enrichment
  12. 2026-09-16 05:15 UTCEPSS rescore
  13. 2026-09-15 09:30 UTCEG score recompute
  14. 2026-09-15 09:30 UTCGHSA enrichment
  15. 2026-09-15 03:12 UTCEPSS rescore
  16. 2026-09-15 03:12 UTCEPSS rescore
  17. 2026-09-14 10:58 UTCEG score recompute
  18. 2026-09-14 10:58 UTCGHSA enrichment
  19. 2026-09-13 12:27 UTCEG score recompute
  20. 2026-09-13 12:27 UTCGHSA enrichment
  21. 2026-09-12 13:56 UTCGHSA enrichment
  22. 2026-09-11 15:25 UTCEG score recompute
  23. 2026-09-11 15:25 UTCGHSA enrichment
  24. 2026-09-11 14:53 UTCEPSS rescore
  25. 2026-09-11 14:53 UTCEPSS rescore
Show 8 more
  1. 2026-09-10 16:53 UTCEG score recompute
  2. 2026-09-10 16:53 UTCGHSA enrichment
  3. 2026-09-09 18:21 UTCGHSA enrichment
  4. 2026-09-08 19:49 UTCEG score recompute
  5. 2026-09-08 19:49 UTCGHSA enrichment
  6. 2026-09-08 18:13 UTCEG score recompute
  7. 2026-09-08 16:28 UTCEG score recompute
  8. 2026-09-08 16:25 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-82068?
CVE-2026-82068 is a medium vulnerability published on September 8, 2026. A security issue in MongoDB Server allows an authenticated user with write privileges to trigger a persistent fatal assertion crash by sending specially crafted retryable write commands. The crash state is durably persisted, causing the server process to repeatedly crash on restart and potentially…
When was CVE-2026-82068 disclosed?
CVE-2026-82068 was first published in the National Vulnerability Database on September 8, 2026, with the most recent update on September 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-82068 actively exploited?
CVE-2026-82068 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 78.9% of all scored CVEs.
What is the CVSS score of CVE-2026-82068?
CVE-2026-82068 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-82068?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-82068, 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-82068

Explore →

Is Your Infrastructure Affected by CVE-2026-82068?

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

Start Free Scan →Browse All CVEs