Is CVE-2026-89099 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-89099 being exploited in the wild.

How severe is CVE-2026-89099?

High severity, with a CVSS score of 7.5, published 11 September 2026.

Which products and versions are affected?

MongoDB Server 7.0 before 7.0.43, 8.0 before 8.0.32, 8.3 before 8.3.11, 9.0 before 9.0.1, 9.1 before 9.1.0-rc0.

Is there a fix for CVE-2026-89099?

A patch was published on 2026-09-01: Fixes released in Server 7.0.43, 8.0.32, 8.3.11, and 9.0.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-89099 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-89099?

Check whether you run MongoDB Server at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-89099: MongoDB Server race condition in document value layer

CVE-2026-89099 · Severity: high · CVSS 7.5 · Published 2026-09-11

A race condition in MongoDB Server's document processing layer allows multiple server threads to access the same memory location without proper synchronization, corrupting internal data structures. An authenticated database user with normal read-write access can trigger this flaw, causing the server to crash and potentially corrupting memory with attacker-controlled content. This impacts the availability and integrity of MongoDB deployments.

Technologies: MongoDB Server. Vendors: MongoDB.

Quick answers

Is CVE-2026-89099 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-89099 being exploited in the wild.
How severe is CVE-2026-89099?: High severity, with a CVSS score of 7.5, published 11 September 2026.
Which products and versions are affected?: MongoDB Server 7.0 before 7.0.43, 8.0 before 8.0.32, 8.3 before 8.3.11, 9.0 before 9.0.1, 9.1 before 9.1.0-rc0.
Is there a fix for CVE-2026-89099?: A patch was published on 2026-09-01: Fixes released in Server 7.0.43, 8.0.32, 8.3.11, and 9.0.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-89099 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-89099?: Check whether you run MongoDB Server at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A race condition in the document value layer permits concurrent server threads to operate on shared internal memory without synchronization, leading to memory corruption. An authenticated user with standard read-write database privileges can trigger this condition over the normal MongoDB client protocol. Exploitation results in server process termination and possible corruption of process memory with user-influenced data.

Affected products

MongoDB Server 7.0 before 7.0.43, 8.0 before 8.0.32, 8.3 before 8.3.11, 9.0 before 9.0.1, 9.1 before 9.1.0-rc0

Timeline

2026-09-11: disclosed
2026-09-01: patched: Fixes released in Server 7.0.43, 8.0.32, 8.3.11, and 9.0.1

References

https://jira.mongodb.org/browse/SERVER-134063

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.