Plan this weekVulnerabilities

MongoDB fixes a critical replica set flaw (CVE-2026-118383): unauthenticated requests can crash a server after a failover, and may allow code execution

MongoDB released fixed versions on 10 November 2026 for CVE-2026-118383, a use-after-free in replica set primary catch-up that requests without authentication can trigger. It can crash the server and, under certain conditions, allow code execution. MongoDB knew of no attacks. Standalone servers are not affected. How to check your replica set and what to do.

How urgent

Plan this week

Who is affected

MongoDB Server replica set members (including shard and config server replica sets) before 4.4.32, 5.0.35, 6.0.30, 7.0.48, 8.0.37, 8.3.16 and 9.0.7; standalone mongod instances are not affected; Atlas clusters are upgraded automatically during maintenance

What to do

Check the version of every replica set member and upgrade to the fixed release for your branch; until then, restrict network access to the database to only the systems that need it; put internet-reachable databases first

Published 12 Nov 2026 · Sources last checked 12 Nov 2026No. 79 / 87

What happened

On 10 November 2026 MongoDB announced fixed releases for CVE-2026-118383, which it rates critical. The CVECVE A public ID number, like CVE-2026-12345, given to one specific security flaw so everyone can talk about the same bug. Tap again to open the glossary record describes it as a pre-authentication use-after-free in the replication component: it can occur when a newly elected replica set primary completes catch-up, and it "can be caused by requests that do not require authentication". The result can be the server terminating unexpectedly or, "under certain conditions", arbitrary code execution in the context of the server process. MongoDB says it found the flaw internally and is not aware of any attempts to take advantage of it.

What the sources say about severity and exposure

  • Severity: the CVE record, filled in by MongoDB, gives CVSSCVSS score A number from 0 to 10 that rates how serious a flaw is in general. From 9.0 up it is called Critical. Tap again to open the glossary v4.0 9.5 and CVSS v3.1 9.0. Both mark attack complexity as high and privileges required as none.
  • Who is exposed: replica set members, including the shard and config server replica sets of sharded clusters. The CVE record says standalone mongod instances are not affected.
  • Affected versions: 4.4 before 4.4.32, 5.0 before 5.0.35, 6.0 before 6.0.30, 7.0 before 7.0.48, 8.0 before 8.0.37, 8.3 before 8.3.16 and 9.0 before 9.0.7. The record lists these as the fixed releases.
  • How it works in a lab: The Hacker News reports that Datadog Security Labs reproduced a crash with two unauthenticated requests. The crash happens only if that member later wins an election while it is still behind the others, and turning on authentication does not stop the two requests on vulnerable versions. The researchers say an attacker cannot make a member fall behind or win an election, or see when either happens. In their lab on 8.0.34 the member crashed, and on the fixed 8.0.37 the requests were rejected as unauthorized.
  • Exploitation: MongoDB says it knows of no attempts. A proof of concept is reported to be on GitHub. We did not find the flaw in CISA's known exploited vulnerabilitiesVulnerability A weakness in software, a setting or a process that an attacker could use to get in or do harm. Tap again to open the glossary catalog.
  • Atlas: MongoDB says Atlas clusters are upgraded to fixed versions during maintenance, and asks customers who defer maintenance to apply the upgrade as soon as possible.

How serious it is

Worth acting on this week if you run a self-managed replica set. What lowers the urgency is that the crash needs a member that is behind to win an election, which an outside attacker cannot cause, and that nobody has reported attacks. What raises it is that no password is needed for the two requests, that the possible result includes code execution, and that a proof of concept is public. Check internet-reachable databases first. A database that should not be reachable from the internet is a problem on its own.

What to do

  1. Find out if you use a replica set: run rs.status() in mongosh. A standalone mongod is not affected. Shard and config server replica sets of a sharded cluster count.
  2. Check every member's version: run db.version() on each member, including members in containers and any that were offline during maintenance.
  3. Upgrade every member to the fixed release for your branch: 4.4.32, 5.0.35, 6.0.30, 7.0.48, 8.0.37, 8.3.16 or 9.0.7 (or later).
  4. If you use Atlas, confirm that maintenance has run and the cluster shows a fixed version. If you deferred maintenance, apply it now.
  5. Until you can upgrade, allow connections to the database only from the systems that need them (firewallFirewall A filter that decides which network traffic may reach a device or service and which is blocked. Tap again to open the glossary or security group). The Hacker News says this limits who can send the two requests but does not fix the flaw.
  6. Look at your logs if you want to check for attempts. The Hacker News lists the signs the Datadog researchers saw in their vulnerable lab run: a "Slow query" entry (ID 51803) for an unauthenticated ping carrying readConcern.afterOpTime that ended in MaxTimeMSExpired, a member entering primary catch-up (ID 21359) and leaving it twice (ID 21363) in one transition, then a fatal signal involving CatchupState::abort_inlock(). A normal election does not point to this flaw.

Steps 1 and 2 are ours.

What we could not confirm

We did not read MongoDB's full advisory page, Datadog Security Labs' own write-up or the two linked Jira issues, so the lab details above come from The Hacker News. We could not confirm that the fixed list is complete: The Hacker News reports that a public proof of concept still crashed 8.2.12, a branch that is not in the affected list and reached end of life on 31 July, so we cannot say which unlisted versions are safe. MongoDB's forum post does not say how the flaw can lead to code execution, and we did not test it ourselves.

Watch the short video

The video loads from YouTube (privacy-enhanced mode) only when you press play.

Comments

No account needed. Add a nickname if you like, or leave it empty to comment anonymously. Comments are reviewed before they appear. Links are not allowed.

    We store your comment, your nickname and a scrambled form of your connection that we use only to limit spam. We do not store your IP address or set cookies. Cloudflare Turnstile checks that you are not a bot.

    Sources and verification

    We use primary sources first and say when we rely on a news report. Dates are the day we last checked each source.

    Spotted a mistake? Email [email protected] and we will correct it and note the change.

    Get the free runbooks

    One-page security checklists for founders who build with AI. You get a confirmation email first, then the runbooks.

    Send me the runbooks