Linux · 
Fedora · Security advisory · July 30, 2026
Fedora · Security advisory · July 30, 2026FEDORA-2026-548235EA3B: rabbitmq-server security update
FEDORA-2026-548235EA3B, released July 30, 2026, fixes 6 CVEs in rabbitmq-server (version 4.0.9-5.fc43). None of them is reported as exploited. Patch Radar priority: High.
High
CVEs closed
6
None rated Critical
Exploited
0
None reported
Highest CVSS
8.8
Base score, 0 to 10
Highest EPSS
0.0284
86th percentile
Priority of the 6 CVEs
Patch now 0
Urgent 0
High 3
Routine 3
Fixed package versions
| Product | Release | Fixed in |
|---|---|---|
| rabbitmq-server | Fedora 43 | 4.0.9-5.fc43 |
CVEs this fix closes
| Priority | CVE | Title | CVSS | EPSS | Exploitation |
|---|---|---|---|---|---|
| High | CVE-2026-57219 | RabbitMQ: Unauthenticated disclosure of OAuth client credentials via an HTTP API endpoint with certain less common OAuth 2 configurations | 7.5 | 0.0284 | None reported |
| High | CVE-2026-57212 | rabbitmq-server: The rabbitmq_management HTTP API accepts oversized valid JSON bodies on with_decode and direct_request | 7.7 | 0.0043 | None reported |
| High | CVE-2026-57215 | RabbitMQ: Direct-reply-to binding persistence can lead to unauthorized reply-channel injection and persistent phantom | 8.8 | 0.0038 | None reported |
| Routine | CVE-2026-57221 | rabbitmq-server: passive queue/exchange declaration bypasses authorization checks, leaking queue metadata to | 5.0 | 0.0041 | None reported |
| Routine | CVE-2026-57213 | RabbitMQ: Stored XSS federation management plugin via unsanitized consumer_tag rendering | 4.8 | 0.0025 | None reported |
| Routine | CVE-2026-44839 | RabbitMQ: Unsanitized vhost names allow for XSS in management UI | 4.8 | 0.0018 | None reported |
Showing 1 to 6 of 6
1
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.