The Daily Byte
Breaking
Welcome to The Daily Byte — real stories from across Pakistan.
Saturday, 21 November 2026 · Pakistan

The Daily Byte

Stories from Pakistan that deserve to be heard

MongoDB CVE-2026-118383 flaw can crash servers

By The Daily Byte ·13 Nov 2026 ·3 min read
A MongoDB office building with the green leaf logo and mongoDB sign on a brick wall

MongoDB has patched a critical vulnerability that lets an unauthenticated attacker crash database servers at the moment they are meant to survive a failure: during failover. The flaw is tracked as CVE-2026-118383 and carries a CVSS 4.0 score of 9.5.

MongoDB announced the fix on 10 November. The company said it found the defect internally and is not aware of any attempts to exploit it in real-world attacks. Datadog Security Labs reproduced the crash and published its findings on 11 November.

The flaw is a use-after-free vulnerability, known as CWE-416, in the replication code that runs when a newly elected replica-set primary completes catch-up. During catch-up, the new primary applies missed operations before it accepts writes.

Two pings plant the crash

An attacker sends two unauthenticated ping commands carrying a readConcern.afterOpTime value to a reachable replica-set member. The requests do not cause an immediate crash. Instead, they create persistent listeners that wait for replication to reach a named point.

The crash comes later, if that member wins an election while still behind another node. The catch-up cleanup then runs twice over memory that has already been freed, and the new primary dies before it accepts a single write. Datadog demonstrated the crash on MongoDB Server 8.0.34 using a four-member replica set, where the targeted member crashed with a segmentation fault.

Enabling authentication does not block the two requests on vulnerable versions, because the ping commands are accepted before login. MongoDB says the flaw may allow code execution under some conditions, but the Datadog researchers did not achieve code execution in their laboratory tests. Their demonstrated result was a database process crash.

Which versions are affected

The flaw affects replica-set members, including shard and config server members in sharded clusters. Standalone mongod instances are not affected.

Fixed releases are 9.0.7, 8.3.16, 8.0.37, 7.0.48, 6.0.30, 5.0.35 and 4.4.32. On the patched 8.0.37 release, Datadog verified that the server rejects both requests as unauthorised when authentication is enabled, and failover completes normally.

The 8.2 branch, which reached end of life on 31 July 2026, receives no patch. Organisations still running it have no upgrade path within that branch and should move to a supported release.

What administrators should do

MongoDB Atlas, the managed cloud database, receives the fixed versions during scheduled maintenance. Self-managed customers must upgrade every replica-set member by hand, including members in containers and any that were offline during maintenance, as well as shard and config server members in sharded clusters.

The flaw was the most severe of 26 vulnerabilities MongoDB fixed in the same November update. Defenders can look in structured logs for COMMAND slow-query events containing ping, readConcern.afterOpTime and a MaxTimeMSExpired error, which may indicate the requests were sent.

Sources: Cyber Press; The Inference.