MongoDB Server
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 9.0.0, < 9.0.7
- >= 8.3.0, < 8.3.16
- >= 8.0.0, < 8.0.37
- >= 7.0.0, < 7.0.48
- >= 6.0.0, < 6.0.30
- >= 5.0.0, < 5.0.35
- >= 4.4.0, < 4.4.32
Fixed in 9.0.7, 8.3.16, 8.0.37, 7.0.48, 6.0.30, 5.0.35, 4.4.32
Mitigation
Upgrade MongoDB Server to 9.0.7 or 8.3.16 or 8.0.37 or 7.0.48 or 6.0.30 or 5.0.35 or 4.4.32 or later.
Timeline
Days relative to CVE publicationFirst public PoC 10 h after publication; not in CISA KEV. First PoC: googlesky/CVE-2026-118383 (created 11 Nov 2026, found by us: 14 Nov 2026).
PoC repositories
Found on GitHub.1 PoCs
PoCs 1
| Repository | Created | Found by us | Stars | Assessment |
|---|---|---|---|---|
| googlesky/CVE-2026-118383 | 11 Nov 2026 +10 h | 14 Nov 2026 | 2 | PoC |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.