CVE-2026-1847
Oplog Fetch Stalling in MongoDB Replica Sets Causes Crash
Publication date: 2026-02-10
Last updated on: 2026-02-25
Assigner: MongoDB, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| mongodb | mongodb | From 7.0.0 (inc) to 7.0.29 (exc) |
| mongodb | mongodb | From 8.0.0 (inc) to 8.0.18 (exc) |
| mongodb | mongodb | From 8.2.0 (inc) to 8.2.4 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-770 | The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability occurs when certain large documents are inserted into a MongoDB replica set. It can cause the secondary members of the replica set to fail to fetch the oplog (operation log) from the primary member. As a result, replication within the replica set can stall, potentially leading to a server crash.
How can this vulnerability impact me? :
The impact of this vulnerability is that it can cause replication to stall in a MongoDB replica set, which may lead to server crashes. This can result in downtime, loss of data synchronization between primary and secondary servers, and potential disruption of services relying on the database.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know