AEGLIX News
A critical pre-authentication flaw in MongoDB Server can cause newly elected replica set primaries to crash when they finish catching up, researchers from Datadog Security Labs reported. The vulnerability affects shard and config server members of sharded clusters, while standalone mongod instances outside replica sets are not impacted. Datadog reproduced the crash in a lab using version 8.0.34, triggering a segmentation fault that left the test cluster without a primary.
The issue is tracked as CVE-2026-118383 and described in the National Vulnerability Database as a use-after-free in the replication component that occurs when a newly elected primary completes catch-up. The condition can be triggered by requests that do not require authentication and may result in the server terminating unexpectedly or, under certain conditions, arbitrary code execution in the context of the server process. Replica set members are affected, including shard and config server replica set members of sharded clusters; standalone mongod instances are not.
Datadog found that two unauthenticated ping commands carrying readConcern.afterOpTime values can plant waiters that persist until the member restarts, rolls back, or steps down from primary. When catch-up ends and cleanup runs twice, it reuses memory that was already freed, causing the new primary to crash before it can accept writes. The proof-of-concept code's reliable mode requires a test-only setting that a remote attacker cannot enable, and its stated impact is a crash or memory corruption with no claim of code execution.
Until upgraded, researchers advise restricting network access to the database to only systems that need it, which limits who can send the two requests but does not fix the flaw.
Report prepared 2026-11-12 · Based on reporting from The Hacker News. Source publication date above; subsequent developments may not be reflected.