# CVE-2026-18888: Memory corruption in BI Connector ODBC Driver

> A buffer overflow in the MongoDB BI Connector ODBC driver allows attackers to crash applications by storing large floating point values.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Aug 2026
- **Updated:** 13 Aug 2026
- **Also known as:** GHSA-hcwq-44xg-qq4g, UBUNTU-CVE-2026-18888

## What is CVE-2026-18888?

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

### Official description

The MongoDB BI Connector ODBC Driver converts floating point column values into text without checking that the result fits within the destination buffer. When an application reads a sufficiently large floating point value as text, the driver may write beyond the end of that buffer and corrupt adjacent memory. A user who can store data in a collection read through the BI Connector could use this to crash the application performing the read.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 1 product.


Products: Mongodb Bi Connector Odbc Driver.

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

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

## Is CVE-2026-18888 being exploited?

There is no known exploitation of CVE-2026-18888 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-19004](https://insights.sbomify.com/CVE-2026-19004/): MongoDB BI Connector ODBC Driver Memory-Safety Issue When Handling Stored Procedure Output Parameters (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)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-18888 is a high-severity memory corruption vulnerability in MongoDB BI Connector ODBC Driver, published on 12 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-18888 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-18888/ (Markdown: https://insights.sbomify.com/CVE-2026-18888/index.md)
```

## Sources

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

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