CVE-2026-9750

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
6.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.5Exploit: NoneExposed: 0

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

An authenticated user can cause a MongoDB server to crash or return incorrect results by creating documents that interfere with internal metadata processing during query execution. This stems from insufficient separation between user-controlled document fields and internal metadata in certain execution paths.

CVSS v3
6.5
EG Score
6.5(medium)
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
Severity65% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
29.3%
KEV
Not listed

Published

June 9, 2026

Last Modified

July 23, 2026

Advisory Details (1)

Auto-updated Jun 15, 2026
No patch confirmed yet.
generic

Loading...

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

Vendor Advisories for CVE-2026-9750(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 8× in last 7d / 50× 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-07-23 14:18 UTCEPSS rescore
  2. 2026-07-23 03:23 UTCEG score recompute
  3. 2026-07-22 14:08 UTCEPSS rescore
  4. 2026-07-21 15:25 UTCEPSS rescore
  5. 2026-07-20 17:08 UTCEPSS rescore
  6. 2026-07-19 14:31 UTCEPSS rescore
  7. 2026-07-19 02:29 UTCEPSS rescore
  8. 2026-07-18 10:04 UTCEPSS rescore
  9. 2026-07-16 23:49 UTCGHSA enrichment
  10. 2026-07-16 17:03 UTCEPSS rescore
  11. 2026-07-15 16:57 UTCEPSS rescore
  12. 2026-07-15 16:45 UTCGHSA enrichment
  13. 2026-07-15 02:00 UTCEPSS rescore
  14. 2026-07-14 14:27 UTCGHSA enrichment
  15. 2026-07-13 22:31 UTCEPSS rescore
  16. 2026-07-13 14:18 UTCGHSA enrichment
  17. 2026-07-13 06:13 UTCEPSS rescore
  18. 2026-07-12 05:46 UTCEPSS rescore
  19. 2026-07-12 03:58 UTCGHSA enrichment
  20. 2026-07-11 08:27 UTCEPSS rescore
  21. 2026-07-11 03:52 UTCGHSA enrichment
  22. 2026-07-09 23:06 UTCGHSA enrichment
  23. 2026-07-09 19:10 UTCEPSS rescore
  24. 2026-07-08 22:30 UTCGHSA enrichment
  25. 2026-07-07 22:24 UTCGHSA enrichment
Show 55 more
  1. 2026-07-06 16:27 UTCEPSS rescore
  2. 2026-07-06 02:23 UTCEPSS rescore
  3. 2026-07-05 13:25 UTCGHSA enrichment
  4. 2026-07-05 02:31 UTCEPSS rescore
  5. 2026-07-04 12:49 UTCGHSA enrichment
  6. 2026-07-04 06:31 UTCEPSS rescore
  7. 2026-07-03 08:36 UTCGHSA enrichment
  8. 2026-07-02 17:02 UTCEPSS rescore
  9. 2026-07-02 07:27 UTCGHSA enrichment
  10. 2026-07-01 15:07 UTCEPSS rescore
  11. 2026-07-01 07:20 UTCGHSA enrichment
  12. 2026-06-30 23:22 UTCEPSS rescore
  13. 2026-06-30 07:14 UTCGHSA enrichment
  14. 2026-06-29 14:06 UTCEPSS rescore
  15. 2026-06-29 06:52 UTCGHSA enrichment
  16. 2026-06-28 14:07 UTCEPSS rescore
  17. 2026-06-28 05:36 UTCGHSA enrichment
  18. 2026-06-28 04:56 UTCEPSS rescore
  19. 2026-06-27 05:27 UTCGHSA enrichment
  20. 2026-06-27 03:08 UTCEPSS rescore
  21. 2026-06-26 05:21 UTCGHSA enrichment
  22. 2026-06-25 13:50 UTCEPSS rescore
  23. 2026-06-25 05:14 UTCGHSA enrichment
  24. 2026-06-24 14:05 UTCEPSS rescore
  25. 2026-06-24 04:55 UTCGHSA enrichment
  26. 2026-06-23 21:33 UTCEPSS rescore
  27. 2026-06-23 04:31 UTCGHSA enrichment
  28. 2026-06-22 14:25 UTCEPSS rescore
  29. 2026-06-22 04:23 UTCGHSA enrichment
  30. 2026-06-21 14:56 UTCEPSS rescore
  31. 2026-06-21 01:59 UTCEPSS rescore
  32. 2026-06-21 01:35 UTCGHSA enrichment
  33. 2026-06-20 00:37 UTCGHSA enrichment
  34. 2026-06-19 19:26 UTCEPSS rescore
  35. 2026-06-19 00:17 UTCGHSA enrichment
  36. 2026-06-18 17:52 UTCEPSS rescore
  37. 2026-06-18 00:06 UTCGHSA enrichment
  38. 2026-06-17 17:53 UTCEPSS rescore
  39. 2026-06-16 23:59 UTCGHSA enrichment
  40. 2026-06-16 17:53 UTCEPSS rescore
  41. 2026-06-15 23:53 UTCGHSA enrichment
  42. 2026-06-15 17:49 UTCEPSS rescore
  43. 2026-06-14 23:48 UTCGHSA enrichment
  44. 2026-06-14 23:18 UTCEPSS rescore
  45. 2026-06-13 23:41 UTCGHSA enrichment
  46. 2026-06-13 23:00 UTCEPSS rescore
  47. 2026-06-12 23:35 UTCGHSA enrichment
  48. 2026-06-12 23:12 UTCEPSS rescore
  49. 2026-06-12 23:12 UTCEPSS rescore
  50. 2026-06-11 23:29 UTCGHSA enrichment
  51. 2026-06-11 14:00 UTCEPSS rescore
  52. 2026-06-10 23:23 UTCGHSA enrichment
  53. 2026-06-10 22:19 UTCEPSS rescore
  54. 2026-06-09 23:17 UTCEG score recompute
  55. 2026-06-09 23:17 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-9750?
CVE-2026-9750 is a medium vulnerability published on June 9, 2026. An authenticated user can cause a MongoDB server to crash or return incorrect results by creating documents that interfere with internal metadata processing during query execution. This stems from insufficient separation between user-controlled document fields and internal metadata in certain…
When was CVE-2026-9750 disclosed?
CVE-2026-9750 was first published in the National Vulnerability Database on June 9, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-9750 actively exploited?
CVE-2026-9750 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 29.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-9750?
CVE-2026-9750 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-9750?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-9750, 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-9750

Explore →

Is Your Infrastructure Affected by CVE-2026-9750?

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

Start Free Scan →Browse All CVEs