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.
CVE-2026-57214
This medium-severity CVE scores 5.4 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 68% 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
- 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 computedSeverity54% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 32%
- KEV
- Not listed
Published
July 10, 2026
Last Modified
July 13, 2026
Advisory Details (6)
Auto-updated Jul 10, 2026Stored XSS in RabbitMQ management UI · Advisory · rabbitmq/rabbitmq-server · GitHub
https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-6jfq-prw2-7rwpRabbitMQ 4.2.5
Patch available: rabbitmq/rabbitmq-server v4.2.5
https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.5Escape 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/15608Escape 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/15606commit b267a290dd89 (rabbitmq/rabbitmq-server)
Fix landed in rabbitmq/rabbitmq-server commit b267a290dd89 — awaiting tagged release
https://github.com/rabbitmq/rabbitmq-server/commit/b267a290dd89e42c6e0256f46fc273a8adb7f3eccommit b0027b6c1ae5 (rabbitmq/rabbitmq-server)
Fix landed in rabbitmq/rabbitmq-server commit b0027b6c1ae5 — awaiting tagged release
https://github.com/rabbitmq/rabbitmq-server/commit/b0027b6c1ae5b869d876e211efe6189ffd92b5c2Vendor 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 / 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 16× in last 7d / 81× 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 120 total refreshes for this CVE.
- 2026-08-30 06:14 UTCEG score recompute
- 2026-08-30 06:14 UTCVendor advisory
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 02:46 UTCEG score recompute
- 2026-08-28 02:46 UTCVendor advisory
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-27 03:11 UTCEG score recompute
- 2026-08-27 03:11 UTCVendor advisory
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-26 03:32 UTCEG score recompute
- 2026-08-26 03:32 UTCVendor advisory
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 03:31 UTCEG score recompute
- 2026-08-25 03:31 UTCVendor advisory
- 2026-08-24 03:56 UTCVendor advisory
- 2026-08-23 04:18 UTCEG score recompute
- 2026-08-23 04:18 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 04:58 UTCVendor advisory
- 2026-08-20 05:23 UTCEG score recompute
- 2026-08-20 05:23 UTCVendor advisory
Show 75 moreShow fewer
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 05:47 UTCEG score recompute
- 2026-08-19 05:47 UTCVendor advisory
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-18 06:11 UTCEG score recompute
- 2026-08-18 06:11 UTCVendor advisory
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 06:04 UTCEG score recompute
- 2026-08-17 06:04 UTCVendor advisory
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 05:32 UTCEG score recompute
- 2026-08-16 05:32 UTCVendor advisory
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 05:57 UTCEG score recompute
- 2026-08-15 05:57 UTCVendor advisory
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 06:22 UTCEG score recompute
- 2026-08-14 06:22 UTCVendor advisory
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 06:46 UTCEG score recompute
- 2026-08-13 06:46 UTCVendor advisory
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 07:11 UTCEG score recompute
- 2026-08-12 07:11 UTCVendor advisory
- 2026-08-11 07:34 UTCEG score recompute
- 2026-08-11 07:34 UTCVendor advisory
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 07:59 UTCEG score recompute
- 2026-08-10 07:59 UTCVendor advisory
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 08:24 UTCEG score recompute
- 2026-08-09 08:24 UTCVendor advisory
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 08:49 UTCEG score recompute
- 2026-08-08 08:49 UTCVendor advisory
- 2026-08-07 09:14 UTCEG score recompute
- 2026-08-07 09:14 UTCVendor advisory
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-06 09:39 UTCEG score recompute
- 2026-08-06 09:39 UTCVendor advisory
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 10:03 UTCEG score recompute
- 2026-08-05 10:03 UTCVendor advisory
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 10:06 UTCEG score recompute
- 2026-08-04 10:06 UTCVendor advisory
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-03 09:54 UTCVendor advisory
- 2026-08-02 10:17 UTCEG score recompute
- 2026-08-02 10:17 UTCVendor advisory
- 2026-08-02 02:27 UTCEPSS rescore
- 2026-08-01 10:41 UTCEG score recompute
- 2026-08-01 10:41 UTCVendor advisory
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-31 11:05 UTCEG score recompute
- 2026-07-31 11:05 UTCVendor advisory
- 2026-07-30 16:28 UTCEPSS rescore
- 2026-07-30 11:22 UTCEG score recompute
- 2026-07-30 11:22 UTCVendor advisory
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-29 11:47 UTCEG score recompute
- 2026-07-28 15:37 UTCEPSS rescore
- 2026-07-28 12:11 UTCEG score recompute
- 2026-07-27 14:14 UTCEPSS rescore
- 2026-07-27 11:43 UTCEG score recompute
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 12:08 UTCEG score recompute
- 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
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
- CVE-2001-0825EG 10.0HIGH
- CVE-2001-1009EG 10.0EPSS p93HIGH
- CVE-2001-0554EG 10.0EPSS p99HIGH
- CVE-2001-1162EG 10.0EPSS p96HIGH
- 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
Frequently asked(5)
What is CVE-2026-57214?
When was CVE-2026-57214 disclosed?
Is CVE-2026-57214 actively exploited?
What is the CVSS score of CVE-2026-57214?
How do I remediate CVE-2026-57214?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-57214
Is Your Infrastructure Affected by CVE-2026-57214?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.