# CVE-2026-81533: MongoDB BI Connector ODBC Driver Memory-Safety Issue When Parsing Oversized LIMIT Values

> An attacker can cause memory corruption or denial of service in applications using the MongoDB BI Connector ODBC Driver by submitting oversized LIMIT values when prefetch is enabled.

- **Severity:** Medium 6.0 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/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:** 28 Aug 2026
- **Updated:** 31 Aug 2026
- **Also known as:** GHSA-gj6m-p8hr-868g

## What is CVE-2026-81533?

CVE-2026-81533 is a medium-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

An application using the MongoDB BI Connector ODBC Driver may encounter a memory-safety issue when a submitted SQL statement contains an unusually long run of digits following a LIMIT clause. The issue occurs only on connections where the driver's optional prefetch setting is enabled, and stems from the driver copying the digit sequence into a fixed-size internal buffer without checking its length. A user able to influence the numeric portion of a LIMIT clause could cause the hosting application process to terminate unexpectedly or corrupt adjacent memory in that process.

Weakness: CWE-121 (Stack-based Buffer Overflow)

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

It affects 1 product.


Products: Mongodb Bi Connector Odbc Driver.

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

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

## Is CVE-2026-81533 being exploited?

There is no known exploitation of CVE-2026-81533 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-81533 and fix it if it is affected.

What it is: CVE-2026-81533 is a medium-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.
Exploitation: There is no known exploitation of CVE-2026-81533 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-81533/ (Markdown: https://insights.sbomify.com/CVE-2026-81533/index.md)
```

## Sources

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

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