Monday 16 November
Global

Your region, kept on this device.

Vulnerability · Mongodb Mongodb

CVE-2026-118383

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.

CVSS score (v4.0)9.5Critical
Fixed in 4.4.32
Not on CISA KEV list

Am I affected?

Sign in and add the software you use to your watchlist: we check it against every new vulnerability.

Show me how to fix it

Timeline

  1. Published by NVD
  2. First covered by RedTeamDaily
  3. Last updated by NVD

Affected products

ProductVersions
Mongodb Mongodbfrom 4.4.0 to before 4.4.32; from 5.0.0 to before 5.0.35; from 6.0.0 to before 6.0.30; from 7.0.0 to before 7.0.48; from 8.0.0 to before 8.0.37; from 8.3.0 to before 8.3.16 and 1 more

Coverage

Datadog Security Labs· · Critical

Critical MongoDB flaw CVE-2026-118383 lets unauthenticated attackers crash database servers

CVE-2026-118383 is a use-after-free flaw in 's replication code, rated 9.5 on CVSS v4.0, and MongoDB announced the fix on 10 November 2026. An unauthenticated attacker can send two ping commands with readConcern.afterOpTime, and if a lagging replica set member later wins an election, the cleanup crashes the server. Only replica set members are affected, not standalone instances, and enabling authentication does not stop the ping step. reproduced a crash on 8.0.34 and found the patched 8.0.37 rejected the requests, though code execution was not achieved.

Sources: NVD and CISA known exploited vulnerabilities catalogue.