CVE-2026-25611: MongoDB Server · Asymmetric Resource Consumption (Amplification)
Affects MongoDB ServerSource CVE Database V5
Not known to be exploited · CVSS 8.7 High · fixed in 8.2.4 : patch MongoDB Server soon.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.8% chance of exploitation in 30 days – higher than 58% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 8.2.4, 8.0.18, 7.0.29
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 10 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Upgrade MongoDB Server to 8.2.4, 8.0.18 or 7.0.29.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| MongoDB IncMongoDB Server | Affected
| Fixed in
|
AI-suggested
1. Apply official patches from MongoDB Inc immediately upon release to remediate the vulnerability. 2. If you cannot patch yet, restrict network access to MongoDB servers using firewalls, VPNs, or network segmentation to limit exposure to trusted hosts only. 3. Disable or restrict remote access to MongoDB instances, especially those exposed to the internet. 4. Implement network intrusion detection and prevention systems (IDS/IPS) to monitor for anomalous or suspicious traffic patterns that could indicate exploitation attempts involving crafted messages. 5. Employ rate limiting and connection throttling on MongoDB endpoints to reduce the risk of resource exhaustion attacks. 6. Regularly audit MongoDB server configurations to ensure authentication and authorization mechanisms are properly enforced, even though this vulnerability does not require authentication. 7. Monitor server resource usage closely to detect early signs of memory exhaustion or abnormal behavior. 8. Consider deploying MongoDB instances behind application-layer proxies or gateways that can filter and validate incoming traffic. 9. Educate IT and security teams about this vulnerability and ensure incident response plans include steps for handling potential DoS attacks on database infrastructure.
Description
A series of specifically crafted, unauthenticated messages can exhaust available memory and crash a MongoDB server.