Skip to content- Sources: discussion
- Summary: MongoDB rates the use-after-free CVE-2026-118383 at 9.5 on CVSS 4.0 and has shipped fixed releases on each affected branch, with Atlas patched during maintenance. Datadog Security Labs reproduced it: pings carrying readConcern.afterOpTime plant waiters that persist, and if that member later wins an election while behind, catch-up cleanup runs twice and the new primary segfaults, as 8.0.34 did in the lab. Fixed 8.0.37 rejects the requests, but a public proof of concept reports the end-of-life 8.2.12 still shows the bug.
- Why it matters: Self-managed replica sets and sharded clusters need the fixed release on every member, because authentication does not block the two requests.
- Background: A MongoDB replica set keeps copies of the same data on several servers, with one primary taking writes. When the primary fails, members elect a new one, which first applies writes it missed in a catch-up phase. The flaw sits in the cleanup at the end of that phase, so it only fires during a failover.
- Follow-up: Whether MongoDB ships an 8.2 fix or confirms the branch is affected.