Quick answers
- Is CVE-2026-81532 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-81532 being exploited in the wild.
- How severe is CVE-2026-81532?
- High severity, with a CVSS score of 8.8, published 28 August 2026.
- Which products and versions are affected?
- MongoDB Connector for BI ODBC driver before 1.4.10.
- Is there a fix for CVE-2026-81532?
- A patch was published on 2026-08-28: Version 1.4.10 released with cursor name truncation logic Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-81532 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-81532?
- Check whether you run MongoDB Bi Connector Odbc Driver or MongoDB Connector for BI 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
This is a classic stack-based buffer overflow vulnerability in the MongoDB Connector for BI ODBC driver. The vulnerable code fails to validate the length of a cursor name in a positioned-cursor SQL statement before copying it into a fixed-length internal buffer when building a diagnostic message. An attacker with the ability to submit SQL queries to an application using this driver can trigger the overflow by providing a cursor name that exceeds the buffer's capacity, overwriting adjacent memory with attacker-controlled data. The impact ranges from denial of service (application crash) to remote code execution. The vulnerability was patched in version 1.4.10 by adding logic to truncate cursor names to fit within the buffer.
Affected products
- MongoDB Connector for BI ODBC driver before 1.4.10
Timeline
- 2026-08-28: disclosed
- 2026-08-28: patched: Version 1.4.10 released with cursor name truncation logic