CVE-2026-57213 Details
Description
RabbitMQ is a messaging and streaming broker. Prior to 3.13.14, 4.0.19, 4.1.10, and 4.2.5, the rabbitmq_federation_management plugin renders the consumer_tag field on the Federation Status page without HTML escaping, allowing a user who can configure a federation upstream or policy to execute JavaScript in the browser of a user viewing that page. This issue is fixed in versions 3.13.14, 4.0.19, 4.1.10, and 4.2.5.
A stored cross-site scripting vulnerability has been identified in the RabbitMQ federation management plugin, affecting versions prior to 3.13.14, 4.0.19, 4.1.10, and 4.2.5. The issue arises because the plugin renders the consumer_tag field on the Federation Status page without proper HTML escaping. This flaw allows a user with the ability to configure a federation upstream or policy to inject JavaScript that is executed in the browser of anyone viewing the page. The vulnerability was reproduced in a local environment with the same conditions as the reported issue.
Users can upgrade to RabbitMQ versions 3.13.14, 4.0.19, 4.1.10, or 4.2.5 to address this vulnerability.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Jul 14, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-79 | Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| broadcom rabbitmq server | >= 3.13.0, < 4.2.5 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 25, 2026 | CVE Translated | [email protected] |
| Jul 14, 2026 | CVE Modified | CISA-ADP |
| Jul 13, 2026 | Initial Analysis | [email protected] |
| Jul 10, 2026 | New CVE Received | [email protected] |