MongoDB Server: Concurrent Execution using Shared Resource with Improper Synchronization
CVE-2026-89099 is a high-severity concurrent execution using shared resource with improper synchronization vulnerability in MongoDB Server from MongoDB, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists versions 8.3.11, 8.0.32, 7.0.43 as the first without the flaw, so updating MongoDB Server to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.32% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update MongoDB Server to 8.3.11 or 8.0.32 or 7.0.43, whichever matches your release line, or a later version.
- Update Mongodb to 7.0.43 or 8.0.32 or 8.3.11, whichever matches your release line, or a later version.
- Read the advisory on jira.mongodb.org for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| MongoDB | MongoDB Server | 8.3.0 up to, but not including, 8.3.11; 8.0 up to, but not including, 8.0.32; 7.0 up to, but not including, 7.0.43 | 8.3.11, 8.0.32, 7.0.43 |
| MongoDB | Mongodb | 7.0.0 up to, but not including, 7.0.43; 8.0.0 up to, but not including, 8.0.32; 8.3.0 up to, but not including, 8.3.11; 9.0.0; 9.1.0 | 7.0.43, 8.0.32, 8.3.11 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- HighSuccess depends on conditions outside the attacker's control.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (mongodb.com).
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 7.7 | High | CNA (mongodb.com) |
| CVSS 3.1 | 7.5 | High | CNA (mongodb.com) |
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Concurrent Execution using Shared Resource with Improper Synchronization
The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.
How developers prevent this class of flaw
- In languages that support it, use synchronization primitives. Only wrap these around critical code to minimize the impact on performance.
- Use thread-safe capabilities such as the data access abstraction in Spring.
- Minimize the usage of shared resources in order to remove as much complexity as possible from the control flow and to reduce the likelihood of unexpected conditions occurring. Additionally, this will minimize the amount of synchronization necessary and may even help to reduce the likelihood of a denial of service where an attacker may be able to repeatedly trigger a critical section (CWE-400).
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
- jira.mongodb.org/browse/SERVER-134063Issue Tracking
Other vulnerabilities in MongoDB Server
- 7.5 High severity
- 8.8 High severity
- 7.1 High severity
- 10.0 Critical severity
- 8.4 High severity
- 7.2 High severity
Recent Concurrent Execution using Shared Resource with Improper Synchronization vulnerabilities
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 8.1 High severity
- 7.0 High severity
- 7.5 High severity
Spotted an error? Tell us.