CVE-2026-19002

HIGHPre-NVD 8.18.1—
EchelonGraph scoreHIGH confidence

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

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

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

A missing bounds check when parsing stored procedure parameter metadata in the MongoDB BI Connector ODBC Driver can result in an out-of-bounds write in the client application process. Triggering this issue requires control over the server the driver connects to, or the ability to respond in its place, in order to return malformed metadata. The resulting memory corruption may cause the client application to terminate abnormally or, under certain conditions, execute unintended code.

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

Published

August 12, 2026

Last Modified

August 13, 2026

Advisory Details (1)

Auto-updated Aug 12, 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-19002(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 29× in last 7d / 34× 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-20 04:46 UTCEG score recompute
  2. 2026-08-20 04:46 UTCGHSA enrichment
  3. 2026-08-19 17:03 UTCEPSS rescore
  4. 2026-08-19 16:30 UTCGHSA enrichment
  5. 2026-08-19 04:14 UTCGHSA enrichment
  6. 2026-08-18 15:58 UTCEG score recompute
  7. 2026-08-18 15:58 UTCGHSA enrichment
  8. 2026-08-18 13:48 UTCEPSS rescore
  9. 2026-08-18 03:42 UTCGHSA enrichment
  10. 2026-08-17 15:26 UTCEG score recompute
  11. 2026-08-17 15:26 UTCGHSA enrichment
  12. 2026-08-17 13:47 UTCEPSS rescore
  13. 2026-08-17 03:10 UTCEG score recompute
  14. 2026-08-17 03:10 UTCGHSA enrichment
  15. 2026-08-16 14:56 UTCEPSS rescore
  16. 2026-08-16 14:54 UTCGHSA enrichment
  17. 2026-08-16 02:38 UTCEG score recompute
  18. 2026-08-16 02:38 UTCGHSA enrichment
  19. 2026-08-16 02:14 UTCEPSS rescore
  20. 2026-08-15 14:23 UTCGHSA enrichment
  21. 2026-08-15 02:06 UTCEG score recompute
  22. 2026-08-15 02:06 UTCGHSA enrichment
  23. 2026-08-15 01:30 UTCEPSS rescore
  24. 2026-08-14 13:51 UTCGHSA enrichment
  25. 2026-08-14 01:35 UTCEG score recompute
Show 9 more
  1. 2026-08-14 01:35 UTCGHSA enrichment
  2. 2026-08-13 22:00 UTCEPSS rescore
  3. 2026-08-13 13:18 UTCEG score recompute
  4. 2026-08-13 13:18 UTCGHSA enrichment
  5. 2026-08-13 09:36 UTCEG score recompute
  6. 2026-08-13 09:36 UTCGHSA enrichment
  7. 2026-08-12 21:20 UTCEG score recompute
  8. 2026-08-12 20:41 UTCEG score recompute
  9. 2026-08-12 20:40 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-19002?
CVE-2026-19002 is a high vulnerability published on August 12, 2026. A missing bounds check when parsing stored procedure parameter metadata in the MongoDB BI Connector ODBC Driver can result in an out-of-bounds write in the client application process. Triggering this issue requires control over the server the driver connects to, or the ability to respond in its…
When was CVE-2026-19002 disclosed?
CVE-2026-19002 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-19002 actively exploited?
CVE-2026-19002 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.0% of all scored CVEs.
What is the CVSS score of CVE-2026-19002?
CVE-2026-19002 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-19002?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-19002, 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-19002

Explore →

Is Your Infrastructure Affected by CVE-2026-19002?

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

Start Free Scan →Browse All CVEs