CVSS 4.0
5.3 mediumCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:NCVE-2026-120820 Uncontrolled Resource Consumption in MongoDB Server Per-Namespace Encrypted-Field Statistics Table Leads to Denial of Service
Medium (5.3) in mongodb mongodb server. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.
On this page
MongoDB Server maintains an in-memory table of per-namespace statistics for operations that carry encrypted-field information. Entries are created for any namespace supplied in a request, with no limit on the number of entries and no way to remove entries that never corresponded to a real collection. A user with basic read privileges who repeatedly issues ordinary read commands referencing arbitrary namespace names may cause the server process to retain steadily increasing amounts of memory and to slow down on the affected code path; the memory is reclaimed only by restarting the process.
Severity
CVSS 3.1
4.3 mediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L- EPSS
- 0.4% estimated probability of exploitation activity in the next 30 days; 30th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
- CISA's assessment (SSVC)
- Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
- CWE
- CWE-770 Allocation of Resources Without Limits or Throttling
- Published
- Modified
- Assigned by
- mongodb (CNA)
- NVD analysis
- Awaiting analysis
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-120820 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-120820?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-120820?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-120820 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:
[](https://cve.bz/cve/CVE-2026-120820)
HTML:
<a href="https://cve.bz/cve/CVE-2026-120820"><img src="https://cve.bz/cve/badge/CVE-2026-120820.svg" alt="CVE-2026-120820"></a>
Affected
- mongodb:mongodb server
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| MongoDB Server | from 9.0.0 before 9.0.7 |
| MongoDB Server | from 8.3.0 before 8.3.16 |
| MongoDB Server | from 8.0.0 before 8.0.37 |
Attack patterns (CAPEC)
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-770 (20).