Quick answers
- Is CVE-2026-19002 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-19002 being exploited in the wild.
- How severe is CVE-2026-19002?
- 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-19002?
- A patch was published on 2026-08-06: Fixed in v1.4.9 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-19002 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-19002?
- 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 missing bounds check (CWE-119) when parsing stored procedure parameter metadata in the MongoDB BI Connector ODBC Driver. An attacker who controls or can intercept the MongoDB server response can return malformed metadata with oversized parameter sizes, triggering an out-of-bounds write in the client application's memory. This requires the attacker to have a network position to intercept or control the server the driver connects to. Successful exploitation results in memory corruption that may cause denial of service (application crash) or, under certain conditions, arbitrary code execution within the client process. The vulnerability was fixed in version 1.4.9 by adding logic to clamp parameter sizes.
Affected products
- MongoDB BI Connector ODBC Driver before 1.4.9
Timeline
- 2026-08-06: patched: Fixed in v1.4.9
- 2026-08-12: disclosed