# CVE-2026-19004: MongoDB BI Connector ODBC Driver Memory-Safety Issue When Handling Stored Procedure Output Parameters

> An attacker controlling a database server can trigger memory corruption in the MongoDB BI Connector ODBC Driver, potentially leading to code execution or information disclosure.

- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Aug 2026
- **Updated:** 13 Aug 2026
- **Also known as:** GHSA-fjxq-47rx-gwhh

## What is CVE-2026-19004?

CVE-2026-19004 is a high-severity memory corruption vulnerability in MongoDB BI Connector ODBC Driver, published on 12 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

An application using the MongoDB BI Connector ODBC Driver may experience a memory-safety issue when processing output parameters from a stored procedure. Triggering this issue requires connecting to an untrusted or impersonated database server that returns crafted metadata. This may result in process termination, disclosure of process memory, or, under certain conditions, arbitrary code execution.

Weakness: CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2026-19004?

It affects 1 product.


Products: Mongodb Bi Connector Odbc Driver.

## How do I fix CVE-2026-19004?

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

## Is CVE-2026-19004 being exploited?

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

## Other vulnerabilities in MongoDB BI Connector ODBC Driver

- [CVE-2026-19001](https://insights.sbomify.com/CVE-2026-19001/): MongoDB BI Connector ODBC driver may write outside an allocated buffer when handling oversized catalog object names (critical 9.5)
- [CVE-2026-19002](https://insights.sbomify.com/CVE-2026-19002/): Crafted database metadata may cause memory corruption in MongoDB BI Connector ODBC Driver (high 8.8)
- [CVE-2026-81532](https://insights.sbomify.com/CVE-2026-81532/): BI Connector ODBC Driver Improper Bounds Checking on Cursor Name Leading to Memory Corruption (high 8.7)
- [CVE-2026-19003](https://insights.sbomify.com/CVE-2026-19003/): Memory corruption in BI Connector ODBC Driver (high 8.4)
- [CVE-2026-18888](https://insights.sbomify.com/CVE-2026-18888/): Memory corruption in BI Connector ODBC Driver (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-19004 and fix it if it is affected.

What it is: CVE-2026-19004 is a high-severity memory corruption vulnerability in MongoDB BI Connector ODBC Driver, published on 12 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-19004 in the wild and no public exploit code.

Affected product: MongoDB BI Connector ODBC Driver. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-19004/ (Markdown: https://insights.sbomify.com/CVE-2026-19004/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-19004
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-19004
- OSV: https://osv.dev/vulnerability/CVE-2026-19004

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-19004/
Summaries are generated and may contain mistakes; the official description above is the record.