Critical MongoDB flaw CVE-2026-118383 lets unauthenticated attackers crash database servers
CRITICAL · VULNERABILITYCVE-2026-118383redteam/daily · 4 sources
- Severity
- Critical
- Highest CVSS
- 9.5
- Exploited
- Not known
- Sources
- 4
What happened
MongoDB has fixed a serious flaw that lets someone on the network crash a database server by sending two simple requests, without logging in. The crash only happens in a specific situation, when a server that is behind on recent changes wins a leadership election. MongoDB says it knows of no attacks so far.
Like I’m new · 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
Datadog Security LabsThe Hacker NewsCyber Security NewsGBHackers
Who and what is in it
Companies