CVE-2026-67416 RabbitMQ: AMQP 1.0 symbolic body descriptor prefix collisions bypass validation
- Exploited in the wild
- Not known
- Fix
- Available
What is CVE-2026-67416?
CVE-2026-67416 is a medium-severity vulnerability in rabbitmq-server, published on 14 Oct 2026.
Official 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, the optimized AMQP 1.0 server_mode parser in deps/amqp10_common/src/amqp10_binary_parser.erl matches the textual prefixes of symbolic data, sequence, and value body descriptors without verifying their encoded symbol lengths. An authenticated AMQP 1.0 publisher with write permission can submit a well-formed unknown descriptor that begins with a registered body descriptor, and RabbitMQ misclassifies and stores the bytes as a standard body section. Strict AMQP 1.0 consumers can terminate while decoding the stored entry. For bodies misclassified as data, AMQP 0-9-1 or other cross-protocol conversion performs full body decoding and can terminate the consumer protocol process, with acknowledgement-required delivery permitting repeated failures. Sequence and value classifications are normally transported as opaque encoded payloads on that conversion path. The broker remains alive, and the issue does not bypass routing or authorization. This issue is fixed in versions 4.0.24, 4.1.15, 4.2.10, and 4.3.4.
Which versions are affected by CVE-2026-67416?
1 open source package ship an affected version, including rabbitmq.
| Package | Affected | Fixed in |
|---|---|---|
rabbitmq Bitnami | From 4.0.0 | 4.0.24, 4.1.15, 4.2.10, 4.3.4 |
How do I fix CVE-2026-67416?
Upgrade rabbitmq to a fixed version for your release line: 4.0.24, 4.1.15, 4.2.10 or 4.3.4.
Is CVE-2026-67416 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-67416 exists.
Sources
Also known as BIT-rabbitmq-2026-67416, DEBIAN-CVE-2026-67416, GHSA-p35w-6mx2-q4pc, UBUNTU-CVE-2026-67416.