Servers and applications
CVE-2026-67416
AMQP 1.0 symbolic body descriptor prefix collisions bypass validation
- Severity
- Medium 5.3
- Published
- 23 Jul 2026
- Last changed
- 15 Oct 2026
- Added to UpHeron
- 3 Nov 2026
- Fixed in
- 4.0.24, 4.1.15, 4.2.10, 4.3.4
- Exploit chance
- 0.6% in the next 30 daysHigher than 50% of CVEs. EPSS by FIRST, 19 Nov 2026
- Weakness
- Improper input validation (CWE-20)Uncaught exception (CWE-248)Improper check for unusual conditions (CWE-754)
- Attack
- Over the network · Needs a user account · No user action needed
- Attacker can
- Slow it down
- CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N- Also known as
- GHSA-p35w-6mx2-q4pc
- Sources
- CVE Program, Project advisories (GitHub)
Description
RabbitMQ's optimized AMQP 1.0 server_mode parser recognizes symbolic message body descriptors by matching a fixed textual prefix but ignores the encoded symbol length. A remote AMQP 1.0 publisher can therefore submit a described value whose descriptor merely begins with amqp:data:binary, amqp:amqp-sequence:list, or amqp:amqp-value:*, and RabbitMQ classifies it as the corresponding standard body section.
The primary proof uses the well-formed but unknown descriptor amqp:data:binary@. Structurally inconsistent encodings with truncated or overlong declared lengths reach the same fast path as long as the fixed prefix is physically present. These cases should be distinguished: the primary sample is a valid generic AMQP described value, while some other affected lengths produce malformed encodings.
The accepted bytes are retained through classic, quorum, and stream queues and are forwarded unchanged to AMQP 1.0 consumers. RabbitMQ's normal decoder rejects the unknown descriptor.
Affected software
| Software | Affected versions |
|---|---|
RabbitMQServers and applications · cna:rabbitmq|rabbitmq-server |
|
RabbitMQServers and applications · github:rabbitmq/rabbitmq-server |
|
About RabbitMQ
open source message broker, sometimes referred to as "Rabbit"
- Docker Hub pulls
- 3,918,841,187Docker Hub, 15 Nov 2026
- GitHub stars
- 13,973GitHub, 15 Nov 2026
- Forks
- 4,032GitHub, 15 Nov 2026
- Latest release
- v4.4.0GitHub, 15 Nov 2026
- Released
- 19 Oct 2026GitHub
- Developer
- Jean-Sébastien PédronWikidata
- License
- Mozilla Public License, version 2.0Wikidata
- Written in
- ErlangWikidata
- First published on GitHub
- 20 Sept 2010GitHub
Website Source code Docker image
Release lines
| Release | Latest | Security fixes |
|---|---|---|
| 4.4 | 4.4.0 | Until 31 Jul 2027 |
| 4.3 | 4.3.7 | Until 31 Jan 2027 |
| 4.2 | 4.2.9 | Ended 31 Jul 2026 |
| 4.1 | 4.1.8 | Ended 30 Jan 2026 |
| 4.0 | 4.0.9 | Ended 30 Apr 2025 |
| 3.13 | 3.13.7 | Ended 30 Sept 2024 |
From endoflife.date.
Vulnerabilities in RabbitMQ
- In our list
- 107
- Published in the last 12 months
- 89
- Critical, last 12 months
- 4
- High, last 12 months
- 22
- Known exploited
- 0
- GHSA-3wxh-g236-vm46LDAP authentication failures allow unauthenticated log amplificationHigh 8.2 25 Oct 2026
- GHSA-g73v-gcjq-2g4hAMQP message conversion can repeatedly disconnect AMQP 0-9-1 consumersMedium 6.3 25 Oct 2026
- GHSA-6wvj-vwrc-wcrmHTML injection in management UI OAuth login warningMedium 5.7 25 Oct 2026
- GHSA-mhh3-4wv2-rrj7SASL credentials are not redacted from `amqp10_client` crash dumps and `sys:get_status` outputMedium 5.7 25 Oct 2026
- GHSA-9h6g-46wc-m2f5Memory DoS via incomplete AMQP 0-9-1 messagesHigh 7.1 25 Oct 2026
- GHSA-j6hc-926v-qwq2RabbitMQ STOMP consumers retain OAuth queue access after JWT expirationMedium 4.9 18 Sept 2026
References
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-67416
- GitHub Advisory Database https://github.com/advisories/GHSA-p35w-6mx2-q4pc
- github.com https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-p35w-6mx2-q4pc