CVE-2026-81532 is an out-of-bounds write vulnerability in the MongoDB Connector for BI ODBC driver. When processing a positioned-cursor SQL statement, the driver builds a diagnostic message using the supplied cursor name without first bounding that name to the size of an internal fixed-length buffer. An overlong cursor name can overwrite adjacent memory with attacker-controlled data. MongoDB Connector for BI ODBC driver version 1.4.10 remediates the issue by truncating cursor names to fit the buffer.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A buffer-overflow vulnerability in the MongoDB Connector for BI ODBC driver. An attacker able to submit SQL through an application can use an overlong positioned-cursor name to overwrite adjacent memory during diagnostic-message construction, potentially crashing the host application or executing unintended code within its process.
A high-severity improper-bounds-checking memory-corruption vulnerability in the MongoDB Connector for BI ODBC driver. An attacker able to submit SQL through an application can use an overly long positioned-cursor name to overflow an internal fixed-length buffer, potentially crashing the host process or executing unintended code in that process.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.