Critical MongoDB Flaw Lets Unauthenticated Attackers Set Up a Database Crash During Failover
MongoDB has released fixed versions for a critical flaw, tracked as CVE-2026-118383, that lets an unauthenticated attacker send two requests to a database server and trigger a crash. The crash only happens if that server is later chosen as the new primary (the main server) while it still lacks some recent changes. MongoDB rated the flaw 9.5 out of 10 on the CVSS 4.0 scale. It said it found the issue itself and was not aware of any attempts to exploit it.
The flaw affects members of a replica set, a group of MongoDB servers that keep copies of the same data. It also affects shard and config server members of sharded clusters. A standalone mongod outside any replica set is not affected. Datadog Security Labs reproduced the crash in a lab and noted that turning on authentication does not block the two requests on vulnerable versions. The researchers said an attacker cannot make a server fall behind or win an election, or see when either happens.
MongoDB Atlas clusters receive fixes automatically during maintenance, though customers who defer maintenance should upgrade as soon as possible. Self-managed deployments need the fixed release on every replica set member, and teams should then check each member's version, including containers and any servers offline during maintenance. The 8.2 branch is not listed as affected and reached end of life on July 31, but a public proof of concept reports that 8.2.12 still showed the bug in a lab test using a test-only setting.