Loading story…
MongoDB disclosed five vulnerabilities in the BI Connector ODBC Driver, including one critical flaw and four high-severity issues affecting releases earlier than 1.4.9. Reported impacts include remote code execution, information disclosure, and denial of service, prompting guidance from Italy’s ACN/CSIRT to apply the vendor’s security updates.
One of the high-severity bugs, CVE-2026-19003, is a memory corruption issue in the driver’s setup dialog that can write outside an allocated buffer when a data source with an oversized path is opened and the user triggers file or folder selection. MongoDB said the flaw is not remotely exploitable, but it can still crash the process and, under some build configurations and conditions, lead to unintended code execution in the context of the logged-in user.
See real exploitation activity before you spend the cycle.
3 events from the most recent confirmed update back to the earliest known activity.
MongoDB disclosed CVE-2026-19003, a high-severity memory corruption flaw in the BI Connector ODBC Driver caused by incorrect buffer capacity calculation when the setup dialog opens a malformed data source with an oversized path. MongoDB said the issue is not remotely exploitable but can cause crashes and, in some conditions, unintended code execution in the user's context.
MongoDB published mongo-bi-connector-odbc-driver version 1.4.9, stating that it fixes five security issues: CVE-2026-18888, CVE-2026-19001, CVE-2026-19002, CVE-2026-19003, and CVE-2026-19004. The release notes describe added bounds-checking or clamping logic for large floats, catalog function name lengths, client app integration parameter sizes, DSN path field sizes, and buffers.
Italy's ACN reported five vulnerabilities affecting the MongoDB BI Connector ODBC Driver, including one critical and four high-severity issues. The notice said versions earlier than 1.4.9 are affected and recommended updating according to MongoDB's security bulletins.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See real exploitation activity behind this advisory so you can triage it against everything else in the queue.
3 references tracked. Mallory keeps watching after this page renders.
acn.gov.it
Open sourcecvefeed.io
Open sourcegithub.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
MongoDB disclosed **12 vulnerabilities** across its database drivers, cryptography library, and BI Connector, including six rated High severity. The most severe reported issues include `CVE-2026-81525` (CVSS 8.6), in which namespace injection in the PHP driver can enable cross-tenant database retargeting; `CVE-2026-81522`, involving cross-database write redirection in the C++ driver; and `CVE-2026-81521`, involving injection risks in the Go driver. Debian packages for the PHP, Go, C++ and `libmongocrypt` components remain flagged as unpatched on affected releases, although no public exploits were known at publication. The BI Connector fixes address SQL injection in `SHOW CREATE` output (`CVE-2026-77586`), unauthenticated SASL-session exhaustion (`CVE-2026-81520`), and an ODBC cursor-name buffer overflow that could crash an application or potentially enable code execution (`CVE-2026-81532`). MongoDB's August BI Connector release remediates several of these issues, while ODBC Driver version **1.4.10** adds cursor-name bounds checks. Organizations should inventory MongoDB drivers and BI Connector deployments, promptly apply vendor updates, enforce strict validation of untrusted database object names and connection parameters, and impose authentication-session timeouts and resource limits. MongoDB has also announced that the BI Connector will reach end of life after September 2026, with the MongoDB SQL Interface recommended for new projects.
Aug 29, 2026
MongoDB disclosed multiple vulnerabilities in **MongoDB Server** and the **MongoDB Java Driver**, including one critical issue and at least 16 high-severity flaws that can lead to remote code execution, information disclosure, authentication bypass, data manipulation, and denial of service. National cyber agencies in Italy, Canada, and Guyana published advisories urging organizations to review MongoDB’s security bulletins and update affected deployments. A key server-side issue, **`CVE-2026-18691`** / **`SERVER-130264`**, affects intra-cluster SASL egress connection setup and can allow an attacker with adjacent network access to downgrade authentication to **`PLAIN`**, exposing a cleartext keyfile and potentially enabling authentication as MongoDB’s internal superuser. Advisories say the server flaw affects versions before **`7.0.40`**, **`8.0.29`**, **`8.2.13`**, **`8.3.8`**, and **`9.0.0-rc2`**, while the Java Driver issue **`JAVA-6266`** affects versions **`4.11.0`** through **`5.9.1`** and can expose a proxy password through `ProxySettings.toString`; administrators are advised to upgrade to patched releases immediately.
Aug 14, 2026
Security advisories warned of two severe database software vulnerabilities with immediate internet-facing risk. In MongoDB, an unauthenticated network attacker can trigger an information disclosure flaw—described in some reporting as **MongoBleed**—to make a vulnerable server return sensitive data such as credentials, secrets, and personal information. The issue affects MongoDB releases dating back to about 2017 and stems from insufficient validation in the `zlib` implementation, which can leak uninitialized heap memory allocated to MongoDB. Working exploitation methods are known, and defenders were told to watch for large volumes of malformed or compressed requests, decompression or memory-handling errors, and repeated unauthenticated connections. Patches are available in versions `8.2.3`, `8.0.17`, `7.0.28`, `6.0.27`, `5.0.32`, and `4.4.30`, while end-of-life branches remain unpatched. A separate advisory disclosed a **critical Redis vulnerability** affecting `8.2.1` and earlier when Lua scripting is enabled, which is the default configuration. The flaw is a use-after-free condition that can be triggered by a specially crafted Lua script and may allow **remote arbitrary code execution**, giving an attacker full control of the host running Redis. Officials urged immediate upgrades because the vulnerability is publicly known and exploitation could begin within hours, and they advised organizations to inspect any previously exposed Redis environments for signs of compromise. Fixed versions were listed as `6.2.20`, `7.2.11`, `7.4.6`, `8.0.4`, and `8.2.2`, alongside renewed guidance that Redis instances should not be exposed directly to the public internet.
Jun 29, 2026