MongoDB fixes CVE-2026-118383, a CVSS 9.5 use-after-free in replica sets triggered without authentication

· CyberSecurity

TLDR

  • CVE-2026-118383, scored CVSS 9.5 by MongoDB, is a replica set use-after-free that requests without authentication can trigger.2
  • Fixed in 9.0.7, 8.3.16, 8.0.37, 7.0.48, 6.0.30, 5.0.35 and 4.4.32; standalone mongod instances are not affected.24
  • MongoDB found it internally, knows of no exploitation attempts and urges Community Edition users to upgrade.1

MongoDB has fixed CVE-2026-118383, a use-after-free in the replication component of MongoDB Server that MongoDB, as the CVE numbering authority, scores 9.5 (critical) under CVSS 4.0.2 The CVE record, which MongoDB issued and the National Vulnerability Database published on 10 November 2026 at 21:18 UTC, says the bug can occur when a newly elected replica set primary completes catch-up.2 It says 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.2 The CVSS 4.0 vector lists a network attack vector, high attack complexity, and no privileges or user interaction required.2 Replica set members are affected, including shard and config server replica set members of sharded clusters; standalone mongod instances are not.2

The record lists seven affected ranges: 9.0.0 up to but not including 9.0.7, 8.3.0 before 8.3.16, 8.0.0 before 8.0.37, 7.0.0 before 7.0.48, 6.0.0 before 6.0.30, 5.0.0 before 5.0.35 and 4.4.0 before 4.4.32.2 KrCERT/CC lists the same ranges in its 10 November advisory and gives 9.0.7, 8.3.16, 8.0.37, 7.0.48, 6.0.30, 5.0.35 and 4.4.32 as the fixed versions.5 MongoDB's Jira ticket SERVER-138175, "Fix use-after-free in CatchupState::abort() reentrancy via _catchupState", is marked Critical (P2), was created on 29 October and resolved on 10 November at 19:18 UTC, and lists fix versions that also include 9.1.0-rc0 and 9.1.0-rc1026.4 The 8.3.16 release notes, dated 10 November, list the CVE among the fixes, along with SERVER-138175 and SERVER-138119, "Allow only system users to use readConcern afterOpTime".3 The CVE record references both tickets.2

In a post on its community forum on 10 November, MongoDB says it identified and fixed the vulnerability, found it internally through its proactive security programme, and is not aware of any attempts to take advantage of it.1 It says it strongly recommends all Community Edition users upgrade to a fixed release as soon as possible.1 For MongoDB Atlas, it says clusters are upgraded automatically to fixed versions during cluster maintenance, and that customers deferring maintenance should apply the upgrade as soon as possible.1

The fix shipped alongside others. The 8.3.16 release notes list fixes for 21 CVEs, and SecurityOnline reports that MongoDB released 9.0.7 and six maintenance updates covering 26 security bugs, of which CVE-2026-118383 and CVE-2026-120808 (CVSS 9.1, a certificate validation bypass in macOS TLS clients) are the two critical ones.36 SecurityOnline lists CVE-2026-118383 as not exploited.6

Why it matters: the flaw sits in replica set members and can be triggered by requests that need no authentication, and MongoDB, which scores it CVSS 9.5 as the CVE numbering authority, tells Community Edition users to upgrade as soon as possible.12

Sources

  1. Important MongoDB security update available (Action Required) - November 10, 2026 (MongoDB Community Hub)
  2. CVE-2026-118383 (NVD CVE API record) (NIST National Vulnerability Database)
  3. Release Notes for MongoDB 8.3 (MongoDB)
  4. Fix use-after-free in CatchupState::abort() reentrancy via _catchupState (SERVER-138175) (MongoDB Jira)
  5. MongoDB 제품 보안 업데이트 권고 (KrCERT/CC)
  6. MongoDB Server 9.0.7 Fixes CVE-2026-118383 Use-After-Free (SecurityOnline)