cve.bz

CVE-2026-120828 Memory exhaustion via abandoned far-future read-concern waiters in disaggregated storage

8.7 highEPSS 0.5%

High (8.7) in mongodb mongodb server. EPSS 0.5% estimated probability of exploitation activity in the next 30 days.

On this page
A replica-set database server node does not limit or reclaim internal wait records created while handling a client-supplied read option that names a point in time the node will never reach. A party with network access and no credentials can cause these records to accumulate without bound and persist after the requests end, which may make the server run out of memory and become unavailable.

Severity

CVSS 4.0

8.7 high
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.5% estimated probability of exploitation activity in the next 30 days; 42nd 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: yes · 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 promptExplain CVE-2026-120828 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-120828?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-120828?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-120828 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

CVE-2026-120828

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:

[![CVE-2026-120828](https://cve.bz/cve/badge/CVE-2026-120828.svg)](https://cve.bz/cve/CVE-2026-120828)

HTML:

<a href="https://cve.bz/cve/CVE-2026-120828"><img src="https://cve.bz/cve/badge/CVE-2026-120828.svg" alt="CVE-2026-120828"></a>

Affected

  • mongodb:mongodb server

Versions

From the CNA's record in the CVE List.

ProductAffected
MongoDB Serverfrom 9.0.0 before 9.0.7
MongoDB Serverfrom 8.3.0 before 8.3.16
MongoDB Serverfrom 8.0.0 before 8.0.37
MongoDB Serverfrom 7.0.0 before 7.0.48
MongoDB Serverfrom 6.0.0 before 6.0.30
MongoDB Serverfrom 5.0.0 before 5.0.35
MongoDB Serverfrom 4.4.0 before 4.4.32

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).

References

Check your stackJSON