CVE-2026-118383 with a CVSS score of 9.5 is a use-after-free vulnerability in MongoDB Server affecting replica set members, including shard and config server members of sharded clusters, while a standalone mongod is not affected. Every earlier version in a branch is affected, back to the branch's first release. The flaw occurs in cleanup that runs when a lagging member finishes catch-up after being elected primary. An unauthenticated attacker can send two ping commands carrying readConcern.afterOpTime values to plant waiters; authentication does not block these requests. The crash requires the targeted member to later win an election while still behind another member, causing the cleanup to run twice and reuse already freed memory. The attacker cannot force the member to lag, win the election, or observe when those events occur. Once the conditions are met, the new primary can crash before accepting writes, leaving a cluster without a primary or causing memory corruption. The flaw may also result in arbitrary code execution in the server process under certain conditions. The impact is denial of service, loss of database availability, and potential compromise of the server process.
We recommend you to update MongoDB Server to version 9.0.7, 8.3.16, 8.0.37, 7.0.48, 6.0.30, 5.0.35, or 4.4.32 or later.[/subscribe_to_unlock_form]
CVE-2026-118383 with a CVSS score of 9.5 is a use-after-free vulnerability in MongoDB Server affecting replica set members, including shard and config server members of sharded clusters, while a standalone mongod is not affected. Every earlier version in a branch is affected, back to the branch's first release. The flaw occurs in cleanup that runs when a lagging member finishes catch-up after being elected primary. An unauthenticated attacker can send two ping commands carrying readConcern.afterOpTime values to plant waiters; authentication does not block these requests. The crash requires the targeted member to later win an election while still behind another member, causing the cleanup to run twice and reuse already freed memory. The attacker cannot force the member to lag, win the election, or observe when those events occur. Once the conditions are met, the new primary can crash before accepting writes, leaving a cluster without a primary or causing memory corruption. The flaw may also result in arbitrary code execution in the server process under certain conditions. The impact is denial of service, loss of database availability, and potential compromise of the server process.
We recommend you to update MongoDB Server to version 9.0.7, 8.3.16, 8.0.37, 7.0.48, 6.0.30, 5.0.35, or 4.4.32 or later.[emaillocker id="1283"]
The following reports contain further technical details:
[/emaillocker]