CVE-2026-5170: Users could trigger a crash of mongod primaries during promotion to sharded
A user with access to the cluster with a limited set of privilege actions can trigger a crash of a mongod process during the limited and unpredictable window when the cluster is being promoted from a replica set to a sharded cluster. This may cause a denial of service by taking down the primary of the replica set.
This issue affects MongoDB Server v8.2 versions prior to 8.2.2, MongoDB Server v8.0 versions between 8.0.18, MongoDB Server v7.0 versions between 7.0.31.
Affected Software
Remediation
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2026-5170?
CVE-2026-5170 is classified as a medium severity vulnerability due to its potential to crash the mongod process during critical operations.
How do I fix CVE-2026-5170?
To fix CVE-2026-5170, upgrade your MongoDB Server to version 8.2.2 or later to address the vulnerability.
Which versions of MongoDB are affected by CVE-2026-5170?
CVE-2026-5170 affects MongoDB Server versions 8.0, 7.0, and earlier versions up to 8.2.1.
Can a low-privileged user exploit CVE-2026-5170?
Yes, a user with limited privileges could potentially exploit CVE-2026-5170 to trigger a crash during cluster promotion.
What operations are compromised by CVE-2026-5170?
CVE-2026-5170 compromises the process of promoting a MongoDB cluster from a replica set to a sharded configuration.