MongoDB Server
Memory exhaustion via abandoned far-future read-concern waiters in disaggregated storage
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.
First public PoC
None yetno public PoC found
Public PoCs00 on GitHub
CVSS8.7high · scored by CNA · CWE-770
CISA KEV
Not listednot known exploited
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
MongoDB MongoDB Server
- >= 9.0.0, < 9.0.7
- >= 8.3.0, < 8.3.16
- >= 8.0.0, < 8.0.37
- >= 7.0.0, < 7.0.48
- >= 6.0.0, < 6.0.30
- >= 5.0.0, < 5.0.35
- >= 4.4.0, < 4.4.32
Fixed in 9.0.7, 8.3.16, 8.0.37, 7.0.48, 6.0.30, 5.0.35, 4.4.32
Mitigation
Upgrade MongoDB Server to 9.0.7 or 8.3.16 or 8.0.37 or 7.0.48 or 6.0.30 or 5.0.35 or 4.4.32 or later.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.