Servers and applications
CVE-2026-121714
AMQP 1.0 post-body properties bypass user-ID validation and reach consumers
- Severity
- Medium 5.3
- Published
- 18 Aug 2026
- Last changed
- 5 Nov 2026
- Added to UpHeron
- 5 Nov 2026
- Fixed in
- 4.3.5
- Weakness
- Improper input validation (CWE-20)Insufficient verification of data authenticity (CWE-345)CWE-436
- Attack
- Over the network · Needs a user account · No user action needed
- CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N- Also known as
- GHSA-6588-rqcr-59pw
- Sources
- Project advisories (GitHub)
Description
RabbitMQ's AMQP 1.0 server parser stops as soon as it encounters the first message body section. It does not validate the remaining message section order. The unparsed tail is stored and forwarded byte-for-byte.
An authenticated AMQP 1.0 publisher can send a valid body followed by a properties section containing a forged user-id. RabbitMQ treats the message as having no user-id when it executes its authenticated publisher check. Downstream AMQP 1.0 clients that do not enforce section ordering parse the late properties and expose the forged identity to the consumer. RabbitMQ's AMQP 1.0-to-0-9-1 conversion path also installs the late properties, exposing the forged user-id to AMQP 0-9-1 consumers.
This creates a message parser differential across RabbitMQ's validation boundary:
The repository's own AMQP 1.0 client accepts properties after the body and exposes the forged user-id.
Affected software
| Software | Affected versions |
|---|---|
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-121714
- GitHub Advisory Database https://github.com/advisories/GHSA-6588-rqcr-59pw
- github.com https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-6588-rqcr-59pw