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

High 8.7 Published 28 Aug 2026 Updated 31 Aug 2026

Attackers can trigger memory corruption via oversized cursor names in SQL statements, potentially causing application crashes or arbitrary code execution.

Exploited in the wild: Not known
Login needed: Any signed-in user
Attackable: Over the internet
Victim action needed: Not needed
Fix: None listed

What is CVE-2026-81532?

CVE-2026-81532 is a high-severity memory corruption vulnerability in MongoDB BI Connector ODBC Driver, published on 28 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

Official 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.

Weakness: CWE-121

Which versions are affected by CVE-2026-81532?

It affects 1 product.

Products include Mongodb Bi Connector Odbc Driver.

How do I fix CVE-2026-81532?

No fix has been published for CVE-2026-81532 yet. Limit exposure of the affected software until one is available.

Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.

Is CVE-2026-81532 being exploited?

There is no known exploitation of CVE-2026-81532 in the wild and no public exploit code.

Sources

Also known as GHSA-ggj7-6w53-qw2v.