Back to feed
19Track

RabbitMQ AMQP 1.0 parser: amplification memory-exhaustion DoS via zero-width array aggregation

rabbitmq-server · CVE-2026-67414
0 news outlets0 CERTs and agencies0 research labs

Assessment: Track

SSVC decision points: exploitation poc, automatable no, technical impact partial, deployment low.

What is it?

RabbitMQ is a messaging and streaming broker. From 4.0.0 until 4.0.24, 4.1.15, 4.2.10, and 4.3.4, deps/amqp10_common/src/amqp10_binary_parser.erl materializes each element of AMQP 1.0 arrays whose shared constructor has zero width, while limiting only the number of elements in each array and not the aggregate arrays in a frame. After completing SASL authentication, a low-privilege client can send an ordinary frame containing many individually permitted arrays, causing a small frame to expand into a very large reader-process heap before later frame validation or authorization. Because deps/rabbit/src/rabbit_amqp_reader.erl clears the pre-authentication max_heap_size guard after login, repeated or concurrent frames can trigger the node-wide memory alarm, block publishers, or exhaust broker memory. This issue is fixed in versions 4.0.24, 4.1.15, 4.2.10, and 4.3.4.

Evidence

Official warnings1National CERTs, government cyber security agencies and the vendor’s own advisories

Exploitation

  • Exploit code published (not verified by us)
  • Exploited in the wild (confirmed by a source)
  • Listed as known exploited (CISA KEV)
CVSS
6.0
EPSS
–
First seen
14 Oct 2026
Status
confirmed

All rabbitmq vulnerabilities