# CVE-2026-67416: RabbitMQ AMQP 1.0 parser descriptor validation bypass

Source: https://junglewise.ai/threats/cve-2026-67416-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-67416 · Severity: info · Published 2026-10-14

RabbitMQ is a message broker that routes and stores messages between applications. An authenticated publisher can exploit a parser flaw to inject malformed AMQP 1.0 messages that are misclassified and stored with corrupted descriptors. Consumers attempting to retrieve these messages may crash when decoding the corrupted data, potentially causing service disruptions and denial of service.

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

## Quick answers

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

**How severe is CVE-2026-67416?** 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-67416?** 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-67416 attacked?** It is attacked over the network.

**Am I affected by CVE-2026-67416?** 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 AMQP 1.0 server-mode parser in amqp10_binary_parser.erl matches symbolic body descriptors (amqp:data:binary, amqp:amqp-sequence:list, amqp:amqp-value) by textual prefix alone without validating the encoded symbol length. An authenticated AMQP 1.0 publisher can submit a well-formed descriptor that begins with a registered body descriptor prefix but differs in actual length, causing misclassification of unknown descriptors as standard body sections. This leads to decoding failures in AMQP 1.0 consumers or consumers using cross-protocol conversion, triggering protocol termination; acknowledgement-required delivery enables repeated failures.

## 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: advisory

## References

- [https://github.com/rabbitmq/rabbitmq-server/commit/c9b4b10c2dbf0f1c89f10b482ac8b45f84dc5954](https://github.com/rabbitmq/rabbitmq-server/commit/c9b4b10c2dbf0f1c89f10b482ac8b45f84dc5954)
- [https://github.com/rabbitmq/rabbitmq-server/commit/d5186e66e056960f58e2d0fbee2fcc66e1ed6fb9](https://github.com/rabbitmq/rabbitmq-server/commit/d5186e66e056960f58e2d0fbee2fcc66e1ed6fb9)

## 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 memory exhaustion](https://junglewise.ai/threats/cve-2026-67414-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)