Skip to content
TrustList
Security advisories

MongoDB fixes pre-auth replica set flaw CVE-2026-118383 (CVSS 9.5)

Editorial

By TrustList Editorial

A request needing no login can crash a newly elected primary or, in some conditions, run code. Fixed in 9.0.7, 8.3.16, 8.0.37, 7.0.48, 6.0.30, 5.0.35 and 4.4.32; Atlas upgrades during maintenance.

About MongoDB fixes pre-auth replica set flaw CVE-2026-118383 (CVSS 9.5)

MongoDB fixes pre-auth replica set flaw CVE-2026-118383 (CVSS 9.5)

10 November 2026: MongoDB has fixed CVE-2026-118383, a use-after-free in the replication code of MongoDB Server rated CVSS 9.5, which a request needing no authentication can trigger on a replica set member just after it is elected primary. MongoDB found it in its own review, knows of no attempt to exploit it, and asks every Community Edition user to upgrade now.

Not yet independently verified. MongoDB says it found the flaw itself and knows of no attempt to exploit it; the only outside analysis we read is Datadog Security Labs' write-up of 11 November, and the flaw is not on CISA's exploited list. We will update this when it can be confirmed, and remove this note.

Which deployments are exposed

The bug sits in the catch-up step a member runs when it wins an election: it first replays writes it missed and only then accepts new ones. MongoDB's CVE record says the condition can be caused by requests that do not require authentication and may crash the server or, under certain conditions, run arbitrary code with the rights of the server process.

Every replica set member is affected, including the shard and config server replica sets inside a sharded cluster. A standalone mongod is not, because it never runs primary catch-up. The CVSS 4.0 vector marks attack complexity as high: an attacker needs a member that has fallen behind and a failover that makes it primary, two conditions Datadog's researchers note an attacker cannot directly control, though a busy cluster produces both in normal life.

Fixed releases by branch

The CVE record lists the first fixed build on each supported line:

  • 9.0 line: 9.0.7
  • 8.3 line: 8.3.16
  • 8.0 line: 8.0.37
  • 7.0 line: 7.0.48
  • 6.0 line: 6.0.30
  • 5.0 line: 5.0.35
  • 4.4 line: 4.4.32

Anything from the first release of each line up to, but not including, those builds is affected. The fix is tracked in MongoDB's issue tracker as SERVER-138119 and SERVER-138175. Distributor packages that carry the fix are also fine, so on a Linux distribution's own MongoDB package the version string to look for is the distributor's patched build rather than the upstream number.

Atlas, self-managed clusters and checks

MongoDB Atlas clusters are moved to fixed versions automatically during their maintenance window. MongoDB's notice singles out customers who defer maintenance and asks them to apply the upgrade as soon as possible, so an Atlas project with a long deferral set is exposed until it lets the window run.

For self-managed clusters the order matters less than coverage: every member of every replica set, including config servers, needs the fixed build, and a rolling upgrade can do that without downtime. After upgrading, check the version each member actually reports rather than the package manager's record. Datadog suggests looking for unusual read concern options in logs from members that are reachable without authentication, and finding members exposed to untrusted networks first. A database port that answers the internet is the case to fix today.

MongoDB's server is listed on TrustList among the 27 products in our NoSQL databases category.

Sources

Categories & features

TrustList Weekly

The week in software and IT, in one email

The news that matters to buyers, new rankings and our own research. Every Thursday, free, and easy to leave.

We will email you to confirm. Unsubscribe with one click in any issue. Privacy policy

You may be interested in