Server crash via uncapped ingress buffers
Published Feb 10, 2026 · Updated Feb 10, 2026
Resource exhaustion in MongoDB Server 7.0 before 7.0.29, 8.0 before 8.0.18, and 8.2 before 8.2.4 allows remote attackers to crash mongod. The ingress networking path accepts crafted messages before authentication and allocates message-compression and network buffers without an effective cap. Repeated messages exhaust server memory and terminate the database process, interrupting availability without granting data access or modification.
Summary
What happened
Resource exhaustion in MongoDB Server 7.0 before 7.0.29, 8.0 before 8.0.18, and 8.2 before 8.2.4 allows remote attackers to crash mongod. The ingress networking path accepts crafted messages before authentication and allocates message-compression and network buffers without an effective cap. Repeated messages exhaust server memory and terminate the database process, interrupting availability without granting data access or modification.
The record
- CVE
- CVE-2026-25611
- Published
- Feb 10, 2026
- Updated
- Feb 10, 2026
- Vendor
- MongoDB
- Product
- MongoDB Server
- Classifications
- CWE-405, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 10, 2026CVE publishedPublication date reported by the CVE source.
- Feb 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=7.0 <7.0.29
- Affected versionversion=8.0 <8.0.18
- Affected versionversion=8.2 <8.2.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo