Skip to main content

Tag: RabbitMQ

Problems with RabbitMQ

IDTitleDescriptionCategoryTechnologyTags
CRE-2024-0007
Critical
Impact: 9/10
Mitigation: 8/10
RabbitMQ Mnesia overloaded recovering persistent queuesThe RabbitMQ cluster is processing a large number of persistent mirrored queues at boot. The underlying Erlang process, Mnesia, is overloaded (`** WARNING ** Mnesia is overloaded`).Message Queue ProblemsrabbitmqKnown ProblemRabbitMQPublic
CRE-2024-0008
High
Impact: 9/10
Mitigation: 6/10
RabbitMQ memory alarmA RabbitMQ node has entered the “memory alarm” state because the total memory used by the Erlang VM (plus allocated binaries, ETS tables, and processes) has exceeded the configured `vm_memory_high_watermark`. While the alarm is active the broker applies flow-control, blocking publishers and pausing most ingress activity to protect itself from running out of RAM.Message Queue ProblemsrabbitmqKnown ProblemRabbitMQPublic
CRE-2025-0063
Medium
Impact: 6/10
Mitigation: 3/10
RabbitMQ disk monitor fails to initialize- RabbitMQ's disk monitor process cannot start or retrieve free‐space metrics, preventing it from detecting low‐disk conditions.Message Queue ProblemsrabbitmqRabbitMQDisk MonitorMonitoringPlugin