CVE-2026-9100

MEDIUMNVD 5.95.9—
EchelonGraph scoreMEDIUM confidence

Score 5.9 from GitHub Security Advisory published 2026-05-20. NVD baseline CVSS 5.9; sources differ by 0.0.

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

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

The MongoDB C Driver's legacy GridFS API accepts malformed file metadata from the database without adequate validation. Crafted documents in a GridFS collection may cause any application that reads those files via the legacy API to either crash (via a division-by-zero) or silently leak process memory contents (via an out-of-bounds read).

CVSS v3
5.9
EG Score
5.9(medium)
EPSS
20.0%
KEV
Not listed

Published

May 20, 2026

Last Modified

May 20, 2026

Advisory Details (1)

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

Loading...

https://jira.mongodb.org/browse/CDRIVER-6281

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

Frequently asked(5)

What is CVE-2026-9100?
CVE-2026-9100 is a medium vulnerability published on May 20, 2026. The MongoDB C Driver's legacy GridFS API accepts malformed file metadata from the database without adequate validation. Crafted documents in a GridFS collection may cause any application that reads those files via the legacy API to either crash (via a division-by-zero) or silently leak process…
When was CVE-2026-9100 disclosed?
CVE-2026-9100 was first published in the National Vulnerability Database on May 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-9100 actively exploited?
CVE-2026-9100 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 20.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-9100?
CVE-2026-9100 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2026-9100?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-9100, 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-9100

Explore →

Is Your Infrastructure Affected by CVE-2026-9100?

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

Start Free Scan →Browse All CVEs