MongoDB Server: Out-of-bounds Write
CVE-2026-8053 is a high-severity out-of-bounds write vulnerability in MongoDB Server from MongoDB, with a CVSS 3.1 base score of 8.8 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 5.0.33, 6.0.28, 7.0.34 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.66% chance of exploitation within 30 days, higher than 52% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update MongoDB Server to 5.0.33 or 6.0.28 or 7.0.34 or 8.0.23, whichever matches your release line, or a later version.
- Update Mongodb to 5.0.33 or 6.0.28 or 7.0.34 or 8.0.23, 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 | 5.0 up to, but not including, 5.0.33; 6.0 up to, but not including, 6.0.28; 7.0 up to, but not including, 7.0.34; 8.0 up to, but not including, 8.0.23; 8.2 up to, but not including, 8.2.9; 8.3 up to, but not including, 8.3.2 | 5.0.33, 6.0.28, 7.0.34, 8.0.23, 8.2.9, 8.3.2 |
| MongoDB | Mongodb | 5.0.0 up to, but not including, 5.0.33; 6.0.0 up to, but not including, 6.0.28; 7.0.0 up to, but not including, 7.0.34; 8.0.0 up to, but not including, 8.0.23; 8.2.0 up to, but not including, 8.2.9; 8.3.0 up to, but not including, 8.3.2 | 5.0.33, 6.0.28, 7.0.34, 8.0.23, 8.2.9, 8.3.2 |
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
- LowNo special conditions are needed; the attack works reliably.
- 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:L/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 | 8.7 | High | CNA (mongodb.com) |
| CVSS 3.1 | 8.8 | High | CNA (mongodb.com) |
Official description
An issue in MongoDB Server's time-series collection implementation allows an authenticated user with database write privileges to trigger an out-of-bounds memory write in the mongod process. The issue results from an inconsistency in the internal field-name-to-index mapping within the time-series bucket catalog. Under certain conditions this can result in arbitrary code execution. This issue impacts MongoDB Server v5.0 versions prior to 5.0.33, v6.0 versions prior to 6.0.28, v7.0 versions prior to 7.0.34, v8.0 versions prior to 8.0.23, v8.2 versions prior to 8.2.9 and v8.3 versions prior to 8.3.2.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Out-of-bounds Write
The product writes data past the end, or before the beginning, of the intended buffer.
How developers prevent this class of flaw
- Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Examples include the Safe C String Library (SafeStr) by Messier and Viega, and the Strsafe.h library from Microsoft. These libraries provide safer versions of overflow-prone string-handling functions.
- Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.
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
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 Out-of-bounds Write vulnerabilities
- 8.1 High severity
- 9.8 Critical severity
- 7.8 High severity
- 7.1 High severity
- 7.8 High severity
- 7.8 High severity
Spotted an error? Tell us.