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 is a use-after-free flaw in MongoDB's replication code, rated 9.5 on CVSS v4.0, and MongoDB announced the fix on 10 November 2026. An unauthenticated attacker can send two ping commands with readConcern.afterOpTime, and if a lagging replica set member later wins an election, the cleanup crashes the server. Only replica set members are affected, not standalone instances, and enabling authentication does not stop the ping step. Datadog Security Labs reproduced a crash on 8.0.34 and found the patched 8.0.37 rejected the requests, though code execution was not achieved.
For IT people · 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