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.
CVE-2026-57213
This medium-severity CVE scores 4.8 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 65% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 4.8
- EG Score
- 4.8(medium)
- EG Risk
- 38(Track)EG Risk 38/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity48% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 35%
- KEV
- Not listed
Published
July 10, 2026
Last Modified
July 14, 2026
Advisory Details (6)
Auto-updated Jul 10, 2026Stored XSS in RabbitMQ federation management plugin via unsanitized consumer_tag rendering · Advisory · rabbitmq/rabbitmq-server · GitHub
https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-qxrp-7cmp-p77hRabbitMQ 4.2.5
Patch available: rabbitmq/rabbitmq-server v4.2.5
https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.5Federation management: use `fmt_string/1` in one more place (backport #15708)
Fix merged in rabbitmq/rabbitmq-server PR #15711 on 2026-03-11 — awaiting tagged release
https://github.com/rabbitmq/rabbitmq-server/pull/15711Federation management: use `fmt_string/1` in one more place
Fix merged in rabbitmq/rabbitmq-server PR #15708 on 2026-03-11 — awaiting tagged release
https://github.com/rabbitmq/rabbitmq-server/pull/15708commit c2d0d69edf01 (rabbitmq/rabbitmq-server)
Fix landed in rabbitmq/rabbitmq-server commit c2d0d69edf01 — awaiting tagged release
https://github.com/rabbitmq/rabbitmq-server/commit/c2d0d69edf01efbd6e87dfb250c373a32da957f8commit 33dedfe4fd53 (rabbitmq/rabbitmq-server)
Fix landed in rabbitmq/rabbitmq-server commit 33dedfe4fd53 — awaiting tagged release
https://github.com/rabbitmq/rabbitmq-server/commit/33dedfe4fd53ff009cc67ab36358d0624c6b2e53Vendor Advisories for CVE-2026-57213(3)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- CVE-2026-57213Microsoft Security Response Center (MSRC)Medium
RabbitMQ: Stored XSS federation management plugin via unsanitized consumer_tag rendering
- RHSA-2026:35940Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
- RHSA-2026:35939Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
Patch Availability(2)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | rabbitmq-server4-3-main-4.3.2-1.hum1 | 2026-07-06 | redhat |
| redhat | rabbitmq-server4-2-main-4.2.8-1.hum1 | 2026-07-06 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(4 across 4 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| rabbitmq-server | 3.10.8-1 ... 4.3.2-4 (38 versions) | — | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| rabbitmq-server | 3.10.8-1.1 ... 4.3.2-4 (27 versions) | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| rabbitmq-server | 4.0.5-10 ... 4.3.2-4 (17 versions) | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| rabbitmq-server | 4.0.5-10 ... 4.3.0-1 (9 versions) | 4.3.0-2 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 14× in last 7d / 77× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 121 total refreshes for this CVE.
- 2026-08-30 06:15 UTCEG score recompute
- 2026-08-30 06:15 UTCVendor advisory
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-27 21:40 UTCEG score recompute
- 2026-08-27 21:40 UTCVendor advisory
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-26 12:53 UTCEG score recompute
- 2026-08-26 12:53 UTCVendor advisory
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 11:05 UTCEG score recompute
- 2026-08-25 11:05 UTCVendor advisory
- 2026-08-24 09:25 UTCVendor advisory
- 2026-08-23 06:03 UTCEG score recompute
- 2026-08-23 06:03 UTCVendor advisory
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 04:42 UTCEG score recompute
- 2026-08-22 04:42 UTCVendor advisory
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 03:02 UTCEG score recompute
- 2026-08-21 03:02 UTCVendor advisory
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 01:37 UTCEG score recompute
- 2026-08-20 01:37 UTCVendor advisory
Show 75 moreShow fewer
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 00:16 UTCEG score recompute
- 2026-08-19 00:16 UTCVendor advisory
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 22:50 UTCEG score recompute
- 2026-08-17 22:50 UTCVendor advisory
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 21:29 UTCEG score recompute
- 2026-08-16 21:29 UTCVendor advisory
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 20:08 UTCEG score recompute
- 2026-08-15 20:08 UTCVendor advisory
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 18:44 UTCEG score recompute
- 2026-08-14 18:44 UTCVendor advisory
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 17:23 UTCVendor advisory
- 2026-08-12 15:58 UTCEG score recompute
- 2026-08-12 15:58 UTCVendor advisory
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-11 14:37 UTCEG score recompute
- 2026-08-11 14:37 UTCVendor advisory
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 13:16 UTCEG score recompute
- 2026-08-10 13:16 UTCVendor advisory
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 11:56 UTCEG score recompute
- 2026-08-09 11:56 UTCVendor advisory
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 10:35 UTCEG score recompute
- 2026-08-08 10:35 UTCVendor advisory
- 2026-08-07 09:13 UTCEG score recompute
- 2026-08-07 09:13 UTCVendor advisory
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-06 07:53 UTCEG score recompute
- 2026-08-06 07:53 UTCVendor advisory
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 06:32 UTCEG score recompute
- 2026-08-05 06:32 UTCVendor advisory
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 10:39 UTCEPSS rescore
- 2026-08-04 03:13 UTCEG score recompute
- 2026-08-04 03:13 UTCVendor advisory
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-03 01:53 UTCEG score recompute
- 2026-08-03 01:53 UTCVendor advisory
- 2026-08-02 02:27 UTCEPSS rescore
- 2026-08-02 00:32 UTCEG score recompute
- 2026-08-02 00:32 UTCVendor advisory
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-31 23:11 UTCVendor advisory
- 2026-07-30 21:48 UTCEG score recompute
- 2026-07-30 21:48 UTCVendor advisory
- 2026-07-30 16:28 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-29 18:36 UTCVendor advisory
- 2026-07-28 17:13 UTCEG score recompute
- 2026-07-28 17:13 UTCVendor advisory
- 2026-07-28 15:37 UTCEPSS rescore
- 2026-07-27 15:32 UTCEG score recompute
- 2026-07-27 15:32 UTCVendor advisory
- 2026-07-27 14:14 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 12:08 UTCEG score recompute
- 2026-07-26 12:08 UTCVendor advisory
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:20 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
- CVE-2001-0825EG 10.0HIGH
- CVE-2001-0554EG 10.0EPSS p99HIGH
- CVE-2001-0414EG 10.0EPSS p100HIGH
- CVE-2001-0191EG 10.0EPSS p92HIGH
- CVE-2001-0301EG 10.0EPSS p91HIGH
- CVE-2001-0197EG 10.0EPSS p96HIGH
- CVE-2001-0233EG 10.0EPSS p96HIGH
- CVE-2001-0010EG 10.0EPSS p98HIGH
- CVE-2001-0011EG 10.0EPSS p94HIGH
- CVE-2001-0013EG 10.0EPSS p96HIGH
Frequently asked(5)
What is CVE-2026-57213?
When was CVE-2026-57213 disclosed?
Is CVE-2026-57213 actively exploited?
What is the CVSS score of CVE-2026-57213?
How do I remediate CVE-2026-57213?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-57213
Is Your Infrastructure Affected by CVE-2026-57213?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.