CVE-2026-89099

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-09-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.

A race condition in the document value layer of MongoDB Server can allow concurrent server threads to operate on the same internal memory without synchronization, leading to memory corruption. An authenticated user holding ordinary read-write privileges on a database may be able to trigger this condition over the normal client protocol, resulting in server termination and potential corruption of process memory with user-influenced content. Successful use of this issue may impact the confidentiality, integrity, and availability of the affected server process.

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

Published

September 11, 2026

Last Modified

September 18, 2026

Advisory Details (1)

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

SAML Login - MongoDB Jira - MongoDB Jira

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

Vendor Advisories for CVE-2026-89099(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 26× in last 7d / 39× 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-20 23:59 UTCEG score recompute
  2. 2026-09-20 23:59 UTCGHSA enrichment
  3. 2026-09-20 20:16 UTCEPSS rescore
  4. 2026-09-20 10:46 UTCGHSA enrichment
  5. 2026-09-19 21:34 UTCEG score recompute
  6. 2026-09-19 21:34 UTCGHSA enrichment
  7. 2026-09-19 08:22 UTCEG score recompute
  8. 2026-09-19 08:22 UTCGHSA enrichment
  9. 2026-09-18 19:28 UTCEPSS rescore
  10. 2026-09-18 19:09 UTCGHSA enrichment
  11. 2026-09-18 10:07 UTCGHSA enrichment
  12. 2026-09-17 20:55 UTCEG score recompute
  13. 2026-09-17 20:55 UTCGHSA enrichment
  14. 2026-09-17 19:32 UTCEPSS rescore
  15. 2026-09-17 07:43 UTCGHSA enrichment
  16. 2026-09-16 18:31 UTCEG score recompute
  17. 2026-09-16 18:31 UTCGHSA enrichment
  18. 2026-09-16 14:09 UTCEPSS rescore
  19. 2026-09-16 05:17 UTCEG score recompute
  20. 2026-09-16 05:17 UTCGHSA enrichment
  21. 2026-09-16 05:15 UTCEPSS rescore
  22. 2026-09-15 16:05 UTCEG score recompute
  23. 2026-09-15 16:05 UTCGHSA enrichment
  24. 2026-09-15 03:12 UTCEPSS rescore
  25. 2026-09-15 02:52 UTCGHSA enrichment
Show 14 more
  1. 2026-09-14 13:39 UTCGHSA enrichment
  2. 2026-09-14 00:24 UTCEG score recompute
  3. 2026-09-14 00:24 UTCGHSA enrichment
  4. 2026-09-13 16:48 UTCEPSS rescore
  5. 2026-09-13 11:12 UTCGHSA enrichment
  6. 2026-09-12 22:00 UTCEG score recompute
  7. 2026-09-12 22:00 UTCGHSA enrichment
  8. 2026-09-12 15:02 UTCEPSS rescore
  9. 2026-09-12 08:48 UTCGHSA enrichment
  10. 2026-09-11 19:35 UTCEG score recompute
  11. 2026-09-11 19:35 UTCGHSA enrichment
  12. 2026-09-11 18:19 UTCEG score recompute
  13. 2026-09-11 17:44 UTCEG score recompute
  14. 2026-09-11 17:43 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-89099?
CVE-2026-89099 is a high vulnerability published on September 11, 2026. A race condition in the document value layer of MongoDB Server can allow concurrent server threads to operate on the same internal memory without synchronization, leading to memory corruption. An authenticated user holding ordinary read-write privileges on a database may be able to trigger this…
When was CVE-2026-89099 disclosed?
CVE-2026-89099 was first published in the National Vulnerability Database on September 11, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-89099 actively exploited?
CVE-2026-89099 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 92.0% of all scored CVEs.
What is the CVSS score of CVE-2026-89099?
CVE-2026-89099 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-89099?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-89099, 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-89099

Explore →

Is Your Infrastructure Affected by CVE-2026-89099?

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

Start Free Scan →Browse All CVEs