Fedora Account System
Red Hat Associate
Red Hat Customer
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 3.13.0 until 3.13.19, 4.0.24, 4.1.15, 4.2.10, and 4.3.5, the MQTT 5 parser in deps/rabbitmq_mqtt/src/rabbit_mqtt_packet.erl accepts Request-Problem-Information on PUBLISH packets even though the property is valid only for CONNECT. An authenticated publisher with topic write permission can cause the broker to store and route that inapplicable property to a separately authenticated matching subscriber. When the subscriber path serializes the outbound PUBLISH, serialise_prop/2 has no matching clause, and the uncontained function_clause exception closes the victim MQTT or Web MQTT connection. The publisher connection and broker remain available, and queued replay, retained-message persistence, and broker-wide denial of service were not established. This issue is fixed in versions 3.13.19, 4.0.24, 4.1.15, 4.2.10, and 4.3.5.
This issue is fixed upstream in RabbitMQ 4.3.5. 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 908f944a1d ("Parse MQTT properties strictly") as rabbitmq-server-4.2.9-4.
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
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
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.
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.
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
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.
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.
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.
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.