Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
9.4

CVE-2026-118383: MongoDB Server replica primary can crash or be hijacked

CVE-2026-118383 · published 11 days ago
Summary

When a MongoDB replica set elects a new primary and it finishes catching up, specially crafted unauthenticated requests can cause the server to shut down or run malicious code. This affects all members of a replica set, including shards and configuration servers in a sharded cluster. Update to the latest MongoDB Server release or apply the provided patches to fix the issue.

What to do
  • Update mongodb mongodb server to version 9.0.7 or later.
Affected software
VendorProductAffected versions
mongodb mongodb server < 9.0.7
mongodb mongodb >= 4.4.0, < 4.4.32
>= 5.0.0, < 5.0.35
>= 6.0.0, < 6.0.30
>= 7.0.0, < 7.0.48
>= 8.0.0, < 8.0.37
>= 8.3.0, < 8.3.16
>= 9.0.0, < 9.0.7
cpe:2.3:a:mongodb:mongodb:*:*:*:*:*:*:*:*
Original advisory text
Pre-authentication use-after-free in MongoDB Server replica set primary catch-up
A use-after-free in the replication component of MongoDB Server can occur when a newly elected replica set primary completes catch-up. The condition can be caused 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 the shard and config server replica set members of sharded clusters; standalone mongod instances are not.
Fix within
Internet-facing 14 days
Internal At next upgrade
  • Not known to be exploited
  • Needs hands-on effort to exploit
  • Gives an attacker full control
Severity
9.4 Critical
Exploitation
<1% chance of attack within 30 days
Type
CWE-416Use After Free
Timeline
Published10 Nov 2026
Updated22 Nov 2026
First seen10 Nov 2026
Sources
CVE-2026-118383 · MITRE
Track software like this
Free during beta