Quick answers
- Is CVE-2026-81533 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-81533 being exploited in the wild.
- How severe is CVE-2026-81533?
- High severity, with a CVSS score of 7.1, published 28 August 2026.
- Which products and versions are affected?
- MongoDB Bi Connector Odbc Driver before 1.4.10.
- Is there a fix for CVE-2026-81533?
- A patch was published on 2026-08-28: Fixed in version 1.4.10 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-81533 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-81533?
- 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
This is a classic buffer overflow vulnerability in the ODBC driver's get_limit method. The vulnerable code copies digit sequences from SQL LIMIT clauses into a fixed-size internal buffer without bounds checking. The vulnerability is triggered only when the driver's prefetch optimization is enabled. An attacker who can influence SQL query construction (via application input, query builder, or direct query submission) can supply an abnormally long numeric LIMIT value to overflow the buffer. Successful exploitation causes denial of service (process crash) or memory corruption that may enable code execution. MongoDB patched this in version 1.4.10 with an added bounds check to the get_limit method.
Affected products
- MongoDB BI Connector ODBC Driver before 1.4.10
Timeline
- 2026-08-28: disclosed
- 2026-08-28: patched: Fixed in version 1.4.10