Quick answers
- Is CVE-2026-19004 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-19004 being exploited in the wild.
- How severe is CVE-2026-19004?
- High severity, with a CVSS score of 8.1, published 12 August 2026.
- Which products and versions are affected?
- MongoDB Bi Connector Odbc Driver before 1.4.9.
- Is there a fix for CVE-2026-19004?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-19004 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-19004?
- 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 memory-safety issue (buffer handling/overflow) in the ODBC driver's output parameter processing logic. It is triggered when connecting to an untrusted or impersonated database server that returns crafted metadata with unclamped buffer sizes. The attack requires network access to a database the application connects to, but does not require authentication to the application itself. Successful exploitation can result in process termination (denial of service), disclosure of process memory contents, or under certain conditions arbitrary code execution. The fix (clamping buffer sizes) was included in version 1.4.9 released on 06 Aug.
Affected products
- MongoDB BI Connector ODBC Driver before 1.4.9
Timeline
- 2026-08-12: disclosed