Bug 2561690 - CVE-2026-67416 rabbitmq-server: rabbitmq-server: Denial of Service via improper AMQP message descriptor validation [fedora-all]
Summary: CVE-2026-67416 rabbitmq-server: rabbitmq-server: Denial of Service via improp...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: rabbitmq-server
Version: rawhide
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Peter Lemenkov
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: {"flaws": ["71bf36e6-a9ef-4e7b-8f75-9...
Depends On:
Blocks: CVE-2026-67416
TreeView+ depends on / blocked
 
Reported: 2026-10-27 10:37 UTC by Vipul Nair
Modified: 2026-11-19 01:45 UTC (History)
2 users (show)

Fixed In Version: rabbitmq-server-4.2.9-5.fc44 rabbitmq-server-4.0.9-7.fc43
Clone Of:
Environment:
Last Closed: 2026-11-13 01:28:14 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Vipul Nair 2026-10-27 10:37:10 UTC
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

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.

Comment 1 Peter Lemenkov 2026-11-02 20:44:35 UTC
This issue is fixed upstream in RabbitMQ 4.3.4. Fedora rawhide and Fedora 45 ship rabbitmq-server-4.3.7-1, so they are already fixed.

For Fedora 44 (4.2.9), the fix is not in any public upstream 4.2.x release. I'm backporting upstream commit d5186e66e0 ("Match exact symbol length when detecting AMQP 1.0 body sections") as rabbitmq-server-4.2.9-4.

Comment 2 Fedora Update System 2026-11-02 21:25:00 UTC
FEDORA-2026-bfe9cc4c24 (rabbitmq-server-4.2.9-4.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-bfe9cc4c24

Comment 3 Fedora Update System 2026-11-02 22:37:48 UTC
FEDORA-2026-baae3b217a (rabbitmq-server-4.0.9-6.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-baae3b217a

Comment 4 Fedora Update System 2026-11-03 02:59:00 UTC
FEDORA-2026-bfe9cc4c24 has been pushed to the Fedora 44 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-bfe9cc4c24`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-bfe9cc4c24

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2026-11-03 03:16:50 UTC
FEDORA-2026-baae3b217a has been pushed to the Fedora 43 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-baae3b217a`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-baae3b217a

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2026-11-04 18:14:45 UTC
FEDORA-2026-ea1afc0a7b (rabbitmq-server-4.0.9-7.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-ea1afc0a7b

Comment 7 Fedora Update System 2026-11-05 03:10:03 UTC
FEDORA-2026-296b2865ba has been pushed to the Fedora 44 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-296b2865ba`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-296b2865ba

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 8 Fedora Update System 2026-11-05 16:08:41 UTC
FEDORA-2026-ea1afc0a7b has been pushed to the Fedora 43 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-ea1afc0a7b`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-ea1afc0a7b

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 9 Fedora Update System 2026-11-13 01:28:14 UTC
FEDORA-2026-296b2865ba (rabbitmq-server-4.2.9-5.fc44) has been pushed to the Fedora 44 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 10 Fedora Update System 2026-11-19 01:45:55 UTC
FEDORA-2026-ea1afc0a7b (rabbitmq-server-4.0.9-7.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.