CVE-2026-67414 rabbitmq CVE debrief

Who should care

RabbitMQ administrators and users, as well as security teams responsible for monitoring and patching RabbitMQ servers, should be aware of this vulnerability and take necessary actions to prevent exploitation. They should update to patched versions and restrict access to authenticated users to prevent memory-exhaustion DoS attacks. Additionally, they should monitor RabbitMQ server memory usage and review compensating controls for exposed systems while remem

Why it matters

This vulnerability affects RabbitMQ servers, allowing authenticated attackers to cause a memory-exhaustion DoS. Administrators should update to patched versions and restrict access to authenticated users.

• Memory exhaustion can lead to node-wide memory alarms, blocking publishers or exhausting broker memory
• Authenticated attackers can exploit this vulnerability to cause a denial-of-service
• RabbitMQ server administrators need to update to patched versions to prevent exploitation

Technical summary

The vulnerability exists in the deps/amqp10_common/src/amqp10_binary_parser.erl file, where arrays with zero width are materialized, leading to a potential memory-exhaustion DoS. This can cause a small frame to expand into a large reader-process heap, triggering a node-wide memory alarm. The issue is fixed in versions 4.0.24, 4.1.15, 4.2.10, and 4.3.4. Administrators should update to patched versions and restrict access to authenticated users to prevent exploitation of this vulnerability in RabbitMQ servers, allowing authenticated attackers to cause a memory-exhaustion DoS.

Defensive priority

Medium

Recommended defensive actions

• Update to RabbitMQ version 4.0.24, 4.1.15, 4.2.10, or 4.3.4
• Restrict access to authenticated users
• Monitor RabbitMQ server memory usage
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability is caused by the materialization of each element of AMQP 1.0 arrays with zero width in the deps/amqp10_common/src/amqp10_binary_parser.erl file. This can lead to a small frame expanding into a large reader-process heap, triggering a node-wide memory alarm.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.