Critical MongoDB flaw CVE-2026-118383 lets unauthenticated attackers crash database servers
- Severity
- Critical
- Highest CVSS
- 9.5
- Exploited
- Not known
- Sources
- 4
What happened
CVE-2026-118383 (CVSS v4.0 9.5) is a pre-auth use-after-free in MongoDB replica set catch-up handling. Two unauthenticated ping commands with readConcern.afterOpTime leave waiters that persist until restart, rollback or step-down; if the lagging member then wins an election, cleanup runs twice on freed memory and the process crashes. Code execution is possible under some conditions but was not demonstrated. Fixed in 9.0.7, 8.3.16, 8.0.37, 7.0.48, 6.0.30, 5.0.35 and 4.4.32; tracked as SERVER-138119 and SERVER-138175. Check every member's version, restrict database ports, and search logs for afterOpTime pings and double catch-up exits before a fatal CatchupState::abortinlock() signal.
For security analysts · Written by AI from 4 sources · Wrong?
What to do
- Upgrade MongoDB to a fixed release such as 8.0.37, 7.0.48 or 9.0.7, matching your release branch.
- Check the version on every replica set member, including containers and nodes that were offline during patching.
- Limit network access to MongoDB ports to the systems that truly need them until patching is complete.
- Review structured logs for ping commands containing readConcern.afterOpTime that show an expired wait.
Written by AI from the sources, checked against them
Vulnerabilities
Full story timeline · 5 updates
- Tue 10 NovemberCVE-2026-118383 published, CVSS 9.5NVD
- Wed 11 NovemberCVE-2026-118383: Use-after-free vulnerability in MongoDBDatadog Security Labs
- Thu 12 NovemberCritical Pre-Auth MongoDB Flaw (CVE-2026-118383) Can Crash Lagging Servers on FailoverThe Hacker News
- Critical MongoDB Flaw Lets Attackers Crash Database Servers With Just Two Ping RequestsCyber Security News
- Critical MongoDB Use-After-Free Vulnerability Allows Remote Code Execution Without AuthenticationGBHackers
Who reported · 4 outlets
Who and what is in it
Companies