SecOraLens
CriticalBreach

Critical MongoDB Flaw Lets Attackers Crash Database Servers With Just Two Ping Requests

Cyber Security News·Source published ·1 min read

What happened?

MongoDB has patched a critical flaw, tracked as CVE-2026-118383, that can let a remote attacker with no login crash a database server using two simple ping requests. The bug carries a CVSS v4.0 score of 9.5. It sits in the replication code that runs when a new primary server finishes catching up. MongoDB announced the fix on November 10, 2026, and said it found the problem internally. The company said it knows of no attempts to abuse it. MongoDB Database Crash Vulnerability The GitHub advisory describes a use-after-free bug.

Key details

  • A critical use-after-free flaw in MongoDB replication code lets unauthenticated remote attackers crash database servers with two ping requests.
  • The bug triggers during replica set catch-up cleanup when a lagging member wins an election and the cleanup runs twice on freed memory.
  • Only replica set members are affected, including shard and config servers in sharded clusters; standalone mongod instances are not vulnerable.
  • Datadog reproduced the crash on MongoDB 8.0.34 causing a segmentation fault, while patched 8.0.37 rejected the requests as Unauthorized.
  • The vulnerability has high attack complexity because the attacker cannot control the timing of the required lag and election events.
  • MongoDB fixed the issue in multiple versions and urges customers to upgrade; network restriction is a temporary mitigation.

What is affected?

  • MongoDB replica set members including shard and config server members in sharded clusters.
  • MongoDB versions prior to the fixed releases: 9.0.7, 8.3.16, 8.0.37, 7.0.48, 6.0.30, 5.0.35, and 4.4.32.

What should defenders look for?

  • Slow-query log entries from ping commands containing readConcern.afterOpTime and an expired wait.
  • A replica set member leaving catch-up twice in one transition followed by a fatal signal mentioning CatchupState::abort_inlock().

Summarised by SecOraLens from Cyber Security News. Always read the original source before acting. How SecOraLens verifies advisories.

What to do next

For CISOs and SOC leads

Brief your board. Brief your team.

Executive risk briefs for governance, technical kill-chains for the SOC — delivered as advisories publish. Critical alerts within 1 hour. No spam, unsubscribe anytime.