home / blog
2026-11-11 · critical
CVE-2026-118383: critical use-after-free in MongoDB
Use-after-free in MongoDB replication coordinator, CVSS 9.0. Urgent patching required before active exploitation.

CVE-2026-118383 is a use-after-free vulnerability in MongoDB Server's replication component. The flaw manifests during catch-up of a newly elected primary in a replica set and can be triggered by unauthenticated requests. Affected are mongod instances acting as replica set members (including shard and config server replica sets in sharded clusters); standalone mongod instances are not vulnerable.
Official CVSS score is 9.0, rated critical. The vulnerability may cause unexpected server termination or, under certain conditions, arbitrary code execution within the mongod process context. Published by NVD on 2026-11-10, public PoC repositories were signaled within 24 hours. Active exploitation in the wild is not confirmed by available data, but PoC availability accelerates the risk timeline.
Administrators must immediately verify which MongoDB Server versions run on replica set deployments. Apply the official MongoDB patch as soon as it is available. In the interim, closely monitor replica logs and server stability metrics; if technically feasible, restrict external exposure of the replication layer. Standalone instances require no urgent action.
At a glance
- What
- Use-after-free in MongoDB Server replication, triggerable without authentication during newly elected primary catch-up. May cause unexpected server termination or arbitrary code execution in the mongod process context.
- Severity
- CVSS 9.0 (critical). Impact on confidentiality, integrity, and availability.
- Affected versions
- Not reported specifically in official NVD documentation.
- Fix
- Official patch required from MongoDB for affected versions. Check MongoDB official advisories.
- Status
- Published NVD 2026-11-10. Public PoC repositories signaled 2026-11-11. Active exploitation in the wild not confirmed by available data.
- Action
- 1) Check MongoDB Server versions in replica set deployments; 2) Apply official patch as soon as available; 3) Monitor replication logs and stability metrics; 4) Reduce replication layer exposure if feasible.
Sources: NVD, CVE-2026-118383