# CVE-2026-67414: RabbitMQ AMQP 1.0 parser memory exhaustion

Source: https://junglewise.ai/threats/cve-2026-67414-rabbitmq-is-a-messaging-and-streaming-broker-from-4-0-0-until-4-0  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-14. Updated: 2026-10-16  
License: CC BY 4.0 with a link back

CVE-2026-67414 · Severity: info · Published 2026-10-14

RabbitMQ is a message broker that processes data streams across networks. An authenticated attacker can craft specially formatted AMQP 1.0 arrays that expand dramatically in memory on the broker, causing a denial of service that blocks legitimate message publishers and may exhaust the broker's RAM, forcing a restart.

Technologies: [VMware RabbitMQ](https://junglewise.ai/threats/technologies/vmware-rabbitmq). Vendors: [VMware](https://junglewise.ai/threats/vendors/vmware).

## Quick answers

**Is CVE-2026-67414 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-67414 being exploited in the wild.

**How severe is CVE-2026-67414?** Informational severity, published 14 October 2026.

**Which products and versions are affected?** VMware RabbitMQ 4.0.0 to 4.0.23, 4.1.0 to 4.1.14, 4.2.0 to 4.2.9, 4.3.0 to 4.3.3.

**Is there a fix for CVE-2026-67414?** Yes: fixed in RabbitMQ 4.0.24, 4.1.15, 4.2.10, 4.3.4. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-67414 attacked?** It is attacked over the network, in a hosted service.

**Am I affected by CVE-2026-67414?** Check whether you run VMware RabbitMQ at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in RabbitMQ 4.0.24, 4.1.15, 4.2.10, 4.3.4

## Technical details

The amqp10_binary_parser in RabbitMQ incorrectly expands AMQP 1.0 arrays with zero-width element constructors into full Erlang lists, creating a memory mismatch where small wire frames become large heap allocations. After SASL authentication succeeds, the reader process loses its pre-auth heap size guard, allowing repeated or concurrent frames to trigger node-wide memory alarms. The fix encodes such arrays as opaque values rather than materializing them element-by-element.

## Affected products

- VMware RabbitMQ 4.0.0 to 4.0.23, 4.1.0 to 4.1.14, 4.2.0 to 4.2.9, 4.3.0 to 4.3.3

## Timeline

- 2026-10-14: disclosed
- 2026-07-21: patched: Fix committed to main branch

## References

- [https://github.com/rabbitmq/rabbitmq-server/commit/3f0f67dfb7c4390e3cbfa25ab3ee19dcb0845bd4](https://github.com/rabbitmq/rabbitmq-server/commit/3f0f67dfb7c4390e3cbfa25ab3ee19dcb0845bd4)
- [https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.4](https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.4)

## Related threats

- [RabbitMQ MQTT 5 parser invalid property denial of service](https://junglewise.ai/threats/cve-2026-67418-rabbitmq-is-a-messaging-and-streaming-broker-from-3-13-0-until-3)
- [RabbitMQ AMQP 1.0 parser descriptor validation bypass](https://junglewise.ai/threats/cve-2026-67416-rabbitmq-is-a-messaging-and-streaming-broker-from-4-0-0-until-4-0)
- [RabbitMQ Management XSS via queue name in OAuth UI](https://junglewise.ai/threats/cve-2026-67421-rabbitmq-is-a-messaging-and-streaming-broker-from-3-13-0-until-3)
- [RabbitMQ JMS topic exchange denial of service via regex wildcard expansion](https://junglewise.ai/threats/cve-2026-67413-rabbitmq-is-a-messaging-and-streaming-broker-from-4-0-0-until-4-0)
- [RabbitMQ Federation upstream authorization bypass](https://junglewise.ai/threats/cve-2026-67412-rabbitmq-is-a-messaging-and-streaming-broker-from-3-13-0-until-4)