Technology: mongodb

ID	Title	Description	Category	Technology	Tags
CRE-2025-0113 Critical Impact: 10/10 Mitigation: 8/10	MongoDB WiredTiger Cache OOM Kill	Detects MongoDB Out-Of-Memory (OOM) kill caused by WiredTiger cachepressure. This occurs when the cache fills with dirty pages fasterthan they can be evicted, causing uncontrolled memory growth untilthe OS kills the process.	Database Availability	mongodb	MongoDB WiredTiger OOM Kill Memory Pressure Cache Eviction Critical Failure
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 Exhaustion	mongodb	CPU/Memory Exhaustion
CRE-2025-0126 High Impact: 10/10 Mitigation: 7/10	MongoDB Replica Set Primary Election Failure	Detects high-severity MongoDB replica set primary election failures that result in no primary node being available,causing complete service unavailability. This rule targets catastrophic conditions that break replica set consensus: Primary node failures followed by election timeouts where no secondary can become primary Network partitions isolating replica set members and preventing quorum formation Heartbeat failures and connectivity issues leading to election failures Replica set state transitions indicating election problems	Database Problems	mongodb	High Availability Quorum Leader Election Network Timeout Crash Data Loss
CRE-2025-0129 Critical Impact: 10/10 Mitigation: 9/10	MongoDB Crash Loop Due to WiredTiger Metadata Corruption	Detects MongoDB failures where the server enters a crash loop due to corrupted WiredTiger metadata.This prevents startup and often requires manual repair or restoration from backups.	MongoDB Startup Failure	mongodb	MongoDB WiredTiger Metadata Corruption Crash Loop Startup Failure