It can occur when a newly elected replica set primary completes catch-up. MongoDB scores it 9.5 Critical under CVSS 4.0. The CNA also gives it 9.0 Critical under CVSS 3.1.Requests that require no authentication can trigger the condition, according to MongoDB's CVE record. The server may terminate unexpectedly or, under certain conditions, execute arbitrary code in its process. MongoDB said on 10 November that it was unaware of attempts to exploit the flaw.
What it allows
How Can CVE-2026-118383 Affect a Replica Set?
The flaw sits in the replication component during primary catch-up after an election. A request without authentication can reach the vulnerable condition. The documented outcomes are an unexpected server termination or, in some conditions, code execution with the server process's privileges.
That makes replica set topology the first exposure question. Members of a standard replica set qualify. Shard and config server replica set members in sharded clusters qualify too. Standalone mongod instances are outside the affected configuration described by MongoDB.
What Does the Evidence Say About Exploitation?
MongoDB said on 10 November 2026 that it was unaware of attempts to take advantage of the flaw. CVE-2026-118383 was absent from CISA's KEV catalog version 2026.11.10. Neither statement establishes that exploitation is impossible.
On 12 November, a public GitHub repository search returned one repository named for this CVE. Its description calls it a proof of concept, but that claim and its code were not validated. This is a research signal, not evidence of an attack.
Brandefense Blackhole counted seven matching dark-chat posts from 14 August to 12 November 2026. The unit is posts matching this CVE identifier, not unique actors or incidents. Discussion volume does not prove exploitation.
MongoDB's Node.js Driver has a separate DNS SRV host validation issue. See the CVE-2026-126837 driver profile for its affected connection scheme and fixed version; its conditions differ from this server flaw.Who is affected
Which MongoDB Server Versions Need an Upgrade?
MongoDB's 10 November alert lists seven affected branches. Upgrade 9.0 releases before 9.0.7 to 9.0.7 or later. Upgrade 8.3 releases before 8.3.16 to 8.3.16 or later. Upgrade 8.0 releases before 8.0.37 to 8.0.37 or later.
For older branches, use the matching release shown below. Check the branch before scheduling the upgrade.
- 7.0.0 to before 7.0.48: upgrade to 7.0.48 or later.
- 6.0.0 to before 6.0.30: upgrade to 6.0.30 or later.
- 5.0.0 to before 5.0.35: upgrade to 5.0.35 or later.
- 4.4.0 to before 4.4.32: upgrade to 4.4.32 or later.
Confirm each server's running version after maintenance. Use the patch management process to track completion.
MongoDB advises Community Edition users to upgrade promptly. It says Atlas clusters receive fixed versions automatically during cluster maintenance. Administrators deferring Atlas maintenance should apply the upgrade as soon as possible.
Start by inventorying replica set members, including shard and config server members. Record each running branch and version before scheduling maintenance. Standalone mongod instances do not meet the topology condition in the advisory.
Timeline
- 2026-11-10
NVD published the MongoDB CNA record for CVE-2026-118383.
- 2026-11-10
MongoDB announced the fixed releases and urged Community Edition users to upgrade.
What to do
-
Inventory replica set members
Identify every MongoDB replica set member, including shard and config server members. Record the running version and whether Atlas maintenance is deferred.
-
Apply the branch-specific fixed release
Use the fixed release listed above for each member's existing branch. Confirm every member's running version after maintenance.
-
Resume deferred Atlas maintenance
If Atlas maintenance is deferred, schedule the fixed-version upgrade promptly. MongoDB says automatic cluster upgrades occur during maintenance.
-
Review service stability and access
Brandefense recommends reviewing unexpected server restarts and access to replica set members while the upgrade is pending. Investigate anomalies using your normal incident process.
What Brandefense can do
- Watch your stack for exploited flaws
Name the vendors and products you run, and Brandefense alerts you when a CVE in them is exploited.
- See CVE-2026-118383 in Brandefense Atlas
The Atlas record of CVE-2026-118383: severity, exploitation status and the sources behind it.
- Vulnerability intelligence platform
Brandefense Vulnerability Intelligence follows which vulnerabilities attackers are using, so your team can patch what is under attack first.
Frequently Asked Questions
What is CVE-2026-118383?
It is a MongoDB Server replication use-after-free that can occur as a newly elected primary completes catch-up. Unauthenticated requests may trigger a crash or, under certain conditions, arbitrary code execution.
Are standalone MongoDB servers affected?
MongoDB's CVE description excludes standalone mongod instances. Replica set members are affected, including shard and config server replica set members in sharded clusters.
Which versions fix CVE-2026-118383?
MongoDB lists a separate fixed threshold for each of seven affected branches. Check the version list above and upgrade each member to the matching fixed release.
Has MongoDB observed exploitation?
MongoDB said on 10 November 2026 that it was unaware of attempts to exploit the vulnerability. The public repository and dark-chat counts here are research signals, not confirmed incidents.
Sources
- MongoDB Security Update, 10 November 2026MongoDB
- MongoDB AlertsMongoDB
- CVE-2026-118383National Institute of Standards and Technology
- Known Exploited Vulnerabilities CatalogCISA