CVE-2026-57213

MEDIUMNVD 4.84.8—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.8 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 83% 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).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 3 sources updated this weekElevated
4.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.8Exploit: Elevated riskExposed: 0

A fix is available — apply it.

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.

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 computed
Severity48% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
17%
KEV
Not listed

Published

July 10, 2026

Last Modified

July 14, 2026

Advisory Details (6)

Auto-updated Jul 10, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available

Stored 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-p77h
github_release Patch Available

RabbitMQ 4.2.5

Patch available: rabbitmq/rabbitmq-server v4.2.5

https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.5
github_pr

Federation 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/15711
github_pr

Federation 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/15708
github_commit

commit c2d0d69edf01 (rabbitmq/rabbitmq-server)

Fix landed in rabbitmq/rabbitmq-server commit c2d0d69edf01 — awaiting tagged release

https://github.com/rabbitmq/rabbitmq-server/commit/c2d0d69edf01efbd6e87dfb250c373a32da957f8
github_commit

commit 33dedfe4fd53 (rabbitmq/rabbitmq-server)

Fix landed in rabbitmq/rabbitmq-server commit 33dedfe4fd53 — awaiting tagged release

https://github.com/rabbitmq/rabbitmq-server/commit/33dedfe4fd53ff009cc67ab36358d0624c6b2e53

Vendor 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.

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrabbitmq-server4-3-main-4.3.2-1.hum12026-07-06redhat
redhatrabbitmq-server4-2-main-4.2.8-1.hum12026-07-06redhat

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.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 17× in last 7d / 52× 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.

  1. 2026-08-03 10:36 UTCEPSS rescore
  2. 2026-08-03 01:53 UTCEG score recompute
  3. 2026-08-03 01:53 UTCVendor advisory
  4. 2026-08-02 02:27 UTCEPSS rescore
  5. 2026-08-02 00:32 UTCEG score recompute
  6. 2026-08-02 00:32 UTCVendor advisory
  7. 2026-08-01 04:16 UTCEPSS rescore
  8. 2026-07-31 23:11 UTCVendor advisory
  9. 2026-07-30 21:48 UTCEG score recompute
  10. 2026-07-30 21:48 UTCVendor advisory
  11. 2026-07-30 16:28 UTCEPSS rescore
  12. 2026-07-30 01:30 UTCEPSS rescore
  13. 2026-07-30 01:30 UTCEPSS rescore
  14. 2026-07-29 18:36 UTCVendor advisory
  15. 2026-07-28 17:13 UTCEG score recompute
  16. 2026-07-28 17:13 UTCVendor advisory
  17. 2026-07-28 15:37 UTCEPSS rescore
  18. 2026-07-27 15:32 UTCEG score recompute
  19. 2026-07-27 15:32 UTCVendor advisory
  20. 2026-07-27 14:14 UTCEPSS rescore
  21. 2026-07-26 14:54 UTCEPSS rescore
  22. 2026-07-26 14:54 UTCEPSS rescore
  23. 2026-07-26 12:08 UTCEG score recompute
  24. 2026-07-26 12:08 UTCVendor advisory
  25. 2026-07-25 14:18 UTCEPSS rescore
Show 27 more
  1. 2026-07-25 14:18 UTCEPSS rescore
  2. 2026-07-24 14:18 UTCEPSS rescore
  3. 2026-07-24 14:18 UTCEPSS rescore
  4. 2026-07-23 14:18 UTCEPSS rescore
  5. 2026-07-23 03:20 UTCEG score recompute
  6. 2026-07-22 14:08 UTCEPSS rescore
  7. 2026-07-21 15:25 UTCEPSS rescore
  8. 2026-07-20 17:08 UTCEPSS rescore
  9. 2026-07-19 14:31 UTCEPSS rescore
  10. 2026-07-19 14:31 UTCEPSS rescore
  11. 2026-07-19 02:29 UTCEPSS rescore
  12. 2026-07-18 10:04 UTCEPSS rescore
  13. 2026-07-16 17:03 UTCEPSS rescore
  14. 2026-07-15 16:57 UTCEPSS rescore
  15. 2026-07-15 16:57 UTCEPSS rescore
  16. 2026-07-15 02:00 UTCEPSS rescore
  17. 2026-07-15 02:00 UTCEPSS rescore
  18. 2026-07-14 15:20 UTCNVD updateCVSS v3 → 4.8
  19. 2026-07-14 14:30 UTCMITRE cvelistV5CVSS v3 → 5.7
  20. 2026-07-14 00:41 UTCEG score recompute▼ 0.90
  21. 2026-07-13 22:31 UTCEPSS rescore
  22. 2026-07-13 22:08 UTCNVD updateCVSS v3 → 4.8
  23. 2026-07-13 06:13 UTCEPSS rescore
  24. 2026-07-13 06:13 UTCEPSS rescore
  25. 2026-07-12 05:46 UTCEPSS rescore
  26. 2026-07-10 20:38 UTCEG score recompute
  27. 2026-07-10 20:37 UTCMITRE cvelistV5first tracked

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-57213?
CVE-2026-57213 is a medium vulnerability published on July 10, 2026. RabbitMQ is a messaging and streaming broker. Prior to 3.13.14, 4.0.19, 4.1.10, and 4.2.5, the rabbitmqfederationmanagement 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…
When was CVE-2026-57213 disclosed?
CVE-2026-57213 was first published in the National Vulnerability Database on July 10, 2026, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-57213 actively exploited?
CVE-2026-57213 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 83.3% of all scored CVEs.
What is the CVSS score of CVE-2026-57213?
CVE-2026-57213 has a CVSS v3 base score of 4.8 (NVD).
How do I remediate CVE-2026-57213?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-57213, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-57213

Explore →

Is Your Infrastructure Affected by CVE-2026-57213?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs