CVE-2026-19001

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.8Exploit: None knownExposed: 0

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

The MongoDB BI Connector ODBC Driver may write outside the bounds of a fixed-size buffer when an application supplies an unusually long catalog, schema, or object name to a metadata retrieval function. This may result in memory corruption within the calling application's process, leading to abnormal termination and, under certain conditions, the potential for arbitrary code execution.

CVSS v3
9.8
EG Score
9.8(high)
EG Risk
59(Track)
EG Risk 59/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
Severity98% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
31%
KEV
Not listed

Published

August 12, 2026

Last Modified

August 13, 2026

Advisory Details (1)

Auto-updated Aug 20, 2026
Patch available. Sources: github_release.
github_release Patch Available

v1.4.9

Patch available: mongodb/mongo-bi-connector-odbc-driver v1.4.9

https://github.com/mongodb/mongo-bi-connector-odbc-driver/releases/tag/v1.4.9

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-19001?
CVE-2026-19001 is a critical vulnerability published on August 12, 2026. The MongoDB BI Connector ODBC Driver may write outside the bounds of a fixed-size buffer when an application supplies an unusually long catalog, schema, or object name to a metadata retrieval function. This may result in memory corruption within the calling application's process, leading to…
When was CVE-2026-19001 disclosed?
CVE-2026-19001 was first published in the National Vulnerability Database on August 12, 2026, with the most recent update on August 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-19001 actively exploited?
CVE-2026-19001 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 69.0% of all scored CVEs.
What is the CVSS score of CVE-2026-19001?
CVE-2026-19001 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-19001?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-19001, 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-19001

Explore →

Is Your Infrastructure Affected by CVE-2026-19001?

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

Start Free Scan →Browse All CVEs