Skip to main content

Category: MongoDB Resource Exhaustion

MongoDB node becomes unresponsive due to memory or CPU exhaustion under high load

IDTitleDescriptionCategoryTechnologyTags
CRE-2025-0115
High
Impact: 8/10
Mitigation: 6/10
MongoDB client disconnects and socket exceptions under load
  • Under high client load or resource exhaustion (e.g., 1 CPU, 500MB RAM), MongoDB can begin to log a large number of socket disconnections and broken pipe errors.
  • This results in frequent connection churn, interrupted operations, and possible failed writes.
MongoDB Resource ExhaustionmongodbCPU/Memory Exhaustion