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 cache pressure. This occurs when the cache fills with dirty pages faster than they can be evicted, causing uncontrolled memory growth until the OS kills the process. | Database Availability | mongodb | MongoDBWiredTigerOOM KillMemory PressureCache EvictionCritical Failure |
| CRE-2025-0115 High Impact: 0/10 Mitigation: 0/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-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 | MongoDBWiredTigerMetadataCorruptionCrash LoopStartup Failure |