CVE-2026-118383 was published by NVD on November 10, 2026. It affects the replication component of MongoDB Server and can be triggered by requests that don't require authentication.
At minimum, the server crashes. Under certain conditions: arbitrary code execution in the context of the mongod process. NVD has already analyzed the CVE and gives it the maximum score, 10.0.
The Vulnerability
| Field | Value |
|---|---|
| CVE | CVE-2026-118383 |
| CVSS 3.1 (NVD) | 10.0 (CRITICAL) — AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H |
| CVSS 3.1 (MongoDB, CNA) | 9.0 (CRITICAL) — AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H |
| CVSS 4.0 (MongoDB, CNA) | 9.5 (CRITICAL) |
| Type | Use-after-free (CWE-416) |
| Authentication | Not required |
| NVD status | Analyzed |
| NVD publication | 2026-11-10 |
NVD description:
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.
NVD and MongoDB disagree on complexity
The two vectors differ on a single metric: attack complexity. MongoDB uses AC:H (9.0), NVD AC:L (10.0).
MongoDB's reading follows from the description: the bug fires when a newly elected primary finishes catch-up. An election has to happen, which the attacker doesn't necessarily control. NVD doesn't weigh that condition. Either way it stays CRITICAL: PR:N and S:C count for more than the timing window.
Who Is Affected
The description is precise about scope:
- affected: replica set members, including the shard and config server replica set members of a sharded cluster;
- not affected: standalone
mongodinstances.
In practice that covers nearly every production deployment, since replication is the recommended setup for high availability.
Affected Versions
| Branch | Affected versions (NVD) | First version out of range |
|---|---|---|
| 4.4 | 4.4.0 → before 4.4.32 | 4.4.32 |
| 5.0 | 5.0.0 → before 5.0.35 | 5.0.35 |
| 6.0 | 6.0.0 → before 6.0.30 | 6.0.30 |
| 7.0 | 7.0.0 → before 7.0.48 | 7.0.48 |
| 8.0 | 8.0.0 → before 8.0.37 | 8.0.37 |
| 8.3 | 8.3.0 → before 8.3.16 | 8.3.16 |
| 9.0 | 9.0.0 → before 9.0.7 | 9.0.7 |
⚠️ These numbers are bounds from NVD's CPE configuration, not necessarily the release to install. NVD's references are MongoDB Jira tickets SERVER-138119 and SERVER-138175: check the fixed releases for your branch there. Branches missing from this table aren't covered by NVD's data; if you're on an end-of-life branch, the answer is a migration.
Check your version:
db.version()
or mongod --version on the server.
Detection
- Unexpected
mongodcrashes, especially right after a primary election: the most likely outcome of an attempt - Repeated elections in the logs (
rs.status(), election and catch-up messages) - Unauthenticated connections from addresses with no reason to reach the MongoDB port
- Child processes or unusual outbound connections started by
mongod
Mitigation
1. Update every replica set member
The usual rolling procedure: secondaries first, then step down the primary (rs.stepDown()) and update the former primary. On a sharded cluster, don't forget the config servers.
2. Close network access to the MongoDB port
The flaw is triggerable without authentication, so having authentication enabled doesn't protect you. What does is making sure the attacker can't reach the port.
- Bind
mongodto the interfaces it needs only (net.bindIp) - Restrict port 27017 to application servers and the other replica set members
- No direct internet exposure
3. Watch elections
An abnormal election during the exposure window warrants a check of the node involved.
Why Continuous Monitoring of Your Databases Matters
MongoDB often runs on servers owned by application teams, outside the security team's network inventory. Seven branches are affected, each with its own bound: knowing which ones you run is step one.
With cveo.tech, register your MongoDB servers with their exact versions, and get an automatic alert whenever a critical CVE affects them.