CVE-2026-57214

MEDIUMNVD 5.45.4
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.4 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 67% 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
5.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.4Exploit: Elevated riskExposed: 0

A fix is available — apply it.

RabbitMQ is a messaging and streaming broker. Prior to 4.2.5, the RabbitMQ management UI renders the x-internal-purpose queue or exchange argument into an HTML title attribute without proper escaping on the Queues and Exchanges pages, allowing a user with permission to declare a queue or exchange to execute JavaScript in another user's browser. This issue is fixed in version 4.2.5.

CVSS v3
5.4
EG Score
5.4(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity54% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
33%
KEV
Not listed

Published

July 10, 2026

Last Modified

July 13, 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 management UI · Advisory · rabbitmq/rabbitmq-server · GitHub

https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-6jfq-prw2-7rwp
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

Escape x-internal-purpose used by the federation plugin (backport #15606)

Fix merged in rabbitmq/rabbitmq-server PR #15608 on 2026-03-02 — awaiting tagged release

https://github.com/rabbitmq/rabbitmq-server/pull/15608
github_pr

Escape x-internal-purpose used by the federation plugin

Fix merged in rabbitmq/rabbitmq-server PR #15606 on 2026-03-02 — awaiting tagged release

https://github.com/rabbitmq/rabbitmq-server/pull/15606
github_commit

commit b267a290dd89 (rabbitmq/rabbitmq-server)

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

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

commit b0027b6c1ae5 (rabbitmq/rabbitmq-server)

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

https://github.com/rabbitmq/rabbitmq-server/commit/b0027b6c1ae5b869d876e211efe6189ffd92b5c2

Vendor Advisories for CVE-2026-57214(2)

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.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
rabbitmq-server3.10.8-1 ... 4.3.2-4 (38 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
rabbitmq-server3.10.8-1.1 ... 4.3.2-4 (27 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
rabbitmq-server4.0.5-10 ... 4.3.2-4 (17 versions)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
rabbitmq-server4.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 12× in last 7d / 51× 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 148 total refreshes for this CVE.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 05:17 UTCEG score recompute
  3. 2026-09-18 05:17 UTCVendor advisory
  4. 2026-09-17 19:31 UTCEPSS rescore
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-16 05:15 UTCEPSS rescore
  7. 2026-09-15 03:11 UTCEPSS rescore
  8. 2026-09-14 07:48 UTCEG score recompute
  9. 2026-09-14 07:48 UTCVendor advisory
  10. 2026-09-13 16:47 UTCEPSS rescore
  11. 2026-09-13 08:11 UTCEG score recompute
  12. 2026-09-13 08:11 UTCVendor advisory
  13. 2026-09-12 02:49 UTCEG score recompute
  14. 2026-09-12 02:49 UTCVendor advisory
  15. 2026-09-11 14:53 UTCEPSS rescore
  16. 2026-09-10 09:35 UTCEPSS rescore
  17. 2026-09-08 22:01 UTCEPSS rescore
  18. 2026-09-08 02:45 UTCEG score recompute
  19. 2026-09-08 02:45 UTCVendor advisory
  20. 2026-09-07 16:01 UTCEPSS rescore
  21. 2026-09-06 13:47 UTCEPSS rescore
  22. 2026-09-05 21:40 UTCEG score recompute
  23. 2026-09-05 21:40 UTCVendor advisory
  24. 2026-09-04 05:07 UTCEPSS rescore
  25. 2026-09-02 14:12 UTCEPSS rescore
Show 75 more
  1. 2026-09-01 13:54 UTCEPSS rescore
  2. 2026-09-01 04:40 UTCEPSS rescore
  3. 2026-08-30 19:17 UTCEPSS rescore
  4. 2026-08-30 06:14 UTCEG score recompute
  5. 2026-08-30 06:14 UTCVendor advisory
  6. 2026-08-30 01:22 UTCEPSS rescore
  7. 2026-08-28 21:42 UTCEPSS rescore
  8. 2026-08-28 02:46 UTCEG score recompute
  9. 2026-08-28 02:46 UTCVendor advisory
  10. 2026-08-27 14:25 UTCEPSS rescore
  11. 2026-08-27 03:11 UTCEG score recompute
  12. 2026-08-27 03:11 UTCVendor advisory
  13. 2026-08-26 14:46 UTCEPSS rescore
  14. 2026-08-26 03:32 UTCEG score recompute
  15. 2026-08-26 03:32 UTCVendor advisory
  16. 2026-08-25 13:49 UTCEPSS rescore
  17. 2026-08-25 03:31 UTCEG score recompute
  18. 2026-08-25 03:31 UTCVendor advisory
  19. 2026-08-24 03:56 UTCVendor advisory
  20. 2026-08-23 04:18 UTCEG score recompute
  21. 2026-08-23 04:18 UTCVendor advisory
  22. 2026-08-23 00:19 UTCEPSS rescore
  23. 2026-08-22 04:42 UTCEG score recompute
  24. 2026-08-22 04:42 UTCVendor advisory
  25. 2026-08-21 23:49 UTCEPSS rescore
  26. 2026-08-21 04:58 UTCVendor advisory
  27. 2026-08-20 05:23 UTCEG score recompute
  28. 2026-08-20 05:23 UTCVendor advisory
  29. 2026-08-19 17:04 UTCEPSS rescore
  30. 2026-08-19 05:47 UTCEG score recompute
  31. 2026-08-19 05:47 UTCVendor advisory
  32. 2026-08-18 13:48 UTCEPSS rescore
  33. 2026-08-18 06:11 UTCEG score recompute
  34. 2026-08-18 06:11 UTCVendor advisory
  35. 2026-08-17 13:47 UTCEPSS rescore
  36. 2026-08-17 06:04 UTCEG score recompute
  37. 2026-08-17 06:04 UTCVendor advisory
  38. 2026-08-16 14:56 UTCEPSS rescore
  39. 2026-08-16 05:32 UTCEG score recompute
  40. 2026-08-16 05:32 UTCVendor advisory
  41. 2026-08-16 02:14 UTCEPSS rescore
  42. 2026-08-15 05:57 UTCEG score recompute
  43. 2026-08-15 05:57 UTCVendor advisory
  44. 2026-08-15 01:30 UTCEPSS rescore
  45. 2026-08-14 06:22 UTCEG score recompute
  46. 2026-08-14 06:22 UTCVendor advisory
  47. 2026-08-13 22:00 UTCEPSS rescore
  48. 2026-08-13 06:46 UTCEG score recompute
  49. 2026-08-13 06:46 UTCVendor advisory
  50. 2026-08-12 13:51 UTCEPSS rescore
  51. 2026-08-12 07:11 UTCEG score recompute
  52. 2026-08-12 07:11 UTCVendor advisory
  53. 2026-08-11 07:34 UTCEG score recompute
  54. 2026-08-11 07:34 UTCVendor advisory
  55. 2026-08-11 00:00 UTCEPSS rescore
  56. 2026-08-10 07:59 UTCEG score recompute
  57. 2026-08-10 07:59 UTCVendor advisory
  58. 2026-08-09 13:46 UTCEPSS rescore
  59. 2026-08-09 08:24 UTCEG score recompute
  60. 2026-08-09 08:24 UTCVendor advisory
  61. 2026-08-08 16:37 UTCEPSS rescore
  62. 2026-08-08 08:49 UTCEG score recompute
  63. 2026-08-08 08:49 UTCVendor advisory
  64. 2026-08-07 09:14 UTCEG score recompute
  65. 2026-08-07 09:14 UTCVendor advisory
  66. 2026-08-06 13:47 UTCEPSS rescore
  67. 2026-08-06 09:39 UTCEG score recompute
  68. 2026-08-06 09:39 UTCVendor advisory
  69. 2026-08-05 19:17 UTCEPSS rescore
  70. 2026-08-05 10:03 UTCEG score recompute
  71. 2026-08-05 10:03 UTCVendor advisory
  72. 2026-08-04 15:10 UTCEPSS rescore
  73. 2026-08-04 10:06 UTCEG score recompute
  74. 2026-08-04 10:06 UTCVendor advisory
  75. 2026-08-03 10:36 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-57214?
CVE-2026-57214 is a medium vulnerability published on July 10, 2026. RabbitMQ is a messaging and streaming broker. Prior to 4.2.5, the RabbitMQ management UI renders the x-internal-purpose queue or exchange argument into an HTML title attribute without proper escaping on the Queues and Exchanges pages, allowing a user with permission to declare a queue or exchange…
When was CVE-2026-57214 disclosed?
CVE-2026-57214 was first published in the National Vulnerability Database on July 10, 2026, with the most recent update on July 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-57214 actively exploited?
CVE-2026-57214 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 67.3% of all scored CVEs.
What is the CVSS score of CVE-2026-57214?
CVE-2026-57214 has a CVSS v3 base score of 5.4 (NVD).
How do I remediate CVE-2026-57214?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-57214, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-57214

Explore →

Is Your Infrastructure Affected by CVE-2026-57214?

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