# CVE-2026-89099: Race Condition in MongoDB Server Document Value Layer Leads to Memory Corruption

> An authenticated user can trigger a race condition in MongoDB Server causing memory corruption and potential code execution or denial of service.

- **Severity:** High 7.7 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/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:** Yes
- **Published:** 11 Sep 2026
- **Updated:** 11 Sep 2026
- **Also known as:** BIT-mongodb-2026-89099, GHSA-fjcj-f5cf-235q, MINI-73hp-pvc7-87w8, MINI-8454-7hcv-46wr, MINI-g9f4-c8mw-mj44, UBUNTU-CVE-2026-89099

## What is CVE-2026-89099?

CVE-2026-89099 is a high-severity vulnerability in Mongodb Mongodb, published on 11 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A race condition in the document value layer of MongoDB Server can allow concurrent server threads to operate on the same internal memory without synchronization, leading to memory corruption. An authenticated user holding ordinary read-write privileges on a database may be able to trigger this condition over the normal client protocol, resulting in server termination and potential corruption of process memory with user-influenced content. Successful use of this issue may impact the confidentiality, integrity, and availability of the affected server process.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

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

1 open source package ship an affected version, including mongodb. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mongodb` | Bitnami | From 7.0.0 | 7.0.43, 8.0.32, 8.3.11, 9.0.2 |

Products: Mongodb Mongodb.

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

Upgrade mongodb to a fixed version for your release line: 7.0.43, 8.0.32, 8.3.11 or 9.0.2.

## Is CVE-2026-89099 being exploited?

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

## Other vulnerabilities in Mongodb Mongodb

- [CVE-2025-14847](https://insights.sbomify.com/CVE-2025-14847/): MongoDB and MongoDB Server Improper Handling of Length Parameter Inconsistency (high 8.7, exploited in the wild)
- [CVE-2026-82067](https://insights.sbomify.com/CVE-2026-82067/): Auth bypass in MongoDB Server (critical 9.2)
- [CVE-2026-13072](https://insights.sbomify.com/CVE-2026-13072/): MongoDB Improper Input Validation in Compute Mode External Data Processing Leading to Memory Corruption (critical 9.2)
- [CVE-2017-15535](https://insights.sbomify.com/CVE-2017-15535/): Denial of service in n/a (critical 9.1)
- [CVE-2026-18691](https://insights.sbomify.com/CVE-2026-18691/): Improper Authentication in MongoDB Intra-Cluster Connections Allows Credential Exposure (critical 9.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-89099 is a high-severity vulnerability in Mongodb Mongodb, published on 11 Sep 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-89099 in the wild and no public exploit code.

Affected packages and fixed versions:
- mongodb (Bitnami): affected from 7.0.0; fixed in 7.0.43, 8.0.32, 8.3.11, 9.0.2

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-89099/ (Markdown: https://insights.sbomify.com/CVE-2026-89099/index.md)
```

## Sources

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

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