Quick answers
- Is CVE-2026-19001 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-19001 being exploited in the wild.
- How severe is CVE-2026-19001?
- Critical severity, with a CVSS score of 9.8, published 12 August 2026.
- Which products and versions are affected?
- MongoDB Bi Connector Odbc Driver before v1.4.9.
- Is there a fix for CVE-2026-19001?
- A patch was published on 2026-08-06: v1.4.9 released with clamping logic for name lengths Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-19001 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-19001?
- Check whether you run MongoDB Bi Connector Odbc Driver at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a classic stack or heap-based buffer overflow in the MongoDB BI Connector ODBC Driver's metadata retrieval functions. The root cause is insufficient bounds checking when processing catalog, schema, or object name parameters supplied by client applications. An attacker can trigger this by connecting through an ODBC client and supplying crafted metadata queries with excessively long name strings, requiring no authentication bypass. Successful exploitation results in memory corruption, leading to application crashes or, under specific conditions and memory layout, arbitrary code execution within the calling application's address space. Patch v1.4.9 (released August 6, 2026) includes clamping logic to enforce maximum name lengths.
Affected products
- MongoDB BI Connector ODBC Driver before v1.4.9
Timeline
- 2026-08-12: disclosed
- 2026-08-06: patched: v1.4.9 released with clamping logic for name lengths