RabbitMQ: Topic authorization can lead to cross-tenant routing-key bypass
CVE-2026-57217 is fixed in rabbitmq-server on 1 platform, first by DEBIAN-CVE-2026-57217, released July 18, 2026. It is not reported as exploited. Patch Radar priority: Routine.
RabbitMQ is a messaging and streaming broker. Prior to 3.13.15, 4.0.21, 4.1.11, and 4.2.6, RabbitMQ topic authorization can allow restricted topic writes and binds during metadata-store failures because topic-permission lookup errors from Khepri can collapse to undefined, which the internal backend treats as allow. This issue is fixed in versions 3.13.15, 4.0.21, 4.1.11, and 4.2.6.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| rabbitmq-server · Debian 14 | 4.3.0-2 | DEBIAN-CVE-2026-57217 | Jul 18, 2026 |
| rabbitmq-server · opensuse-leap 16.0 | 4.1.5-160000.2.1 | OPENSUSE-SU-2026:21903-1 | Sep 22, 2026 |
| rabbitmq-server · sles 16.0 | 4.1.5-160000.2.1 | SUSE-SU-2026:23869-1 | Sep 22, 2026 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.