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.2%, top 87% 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
13%
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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 18× in last 7d / 49× 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 09:54 UTCVendor advisory
  3. 2026-08-02 10:17 UTCEG score recompute
  4. 2026-08-02 10:17 UTCVendor advisory
  5. 2026-08-02 02:27 UTCEPSS rescore
  6. 2026-08-01 10:41 UTCEG score recompute
  7. 2026-08-01 10:41 UTCVendor advisory
  8. 2026-08-01 04:16 UTCEPSS rescore
  9. 2026-07-31 11:05 UTCEG score recompute
  10. 2026-07-31 11:05 UTCVendor advisory
  11. 2026-07-30 16:28 UTCEPSS rescore
  12. 2026-07-30 11:22 UTCEG score recompute
  13. 2026-07-30 11:22 UTCVendor advisory
  14. 2026-07-30 01:30 UTCEPSS rescore
  15. 2026-07-30 01:30 UTCEPSS rescore
  16. 2026-07-29 11:47 UTCEG score recompute
  17. 2026-07-28 15:37 UTCEPSS rescore
  18. 2026-07-28 12:11 UTCEG score recompute
  19. 2026-07-27 14:14 UTCEPSS rescore
  20. 2026-07-27 11:43 UTCEG score recompute
  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-25 14:18 UTCEPSS rescore
  25. 2026-07-25 14:18 UTCEPSS rescore
Show 24 more
  1. 2026-07-24 14:18 UTCEPSS rescore
  2. 2026-07-24 14:18 UTCEPSS rescore
  3. 2026-07-23 14:18 UTCEPSS rescore
  4. 2026-07-23 03:20 UTCEG score recompute
  5. 2026-07-22 14:08 UTCEPSS rescore
  6. 2026-07-21 15:25 UTCEPSS rescore
  7. 2026-07-20 17:08 UTCEPSS rescore
  8. 2026-07-19 14:31 UTCEPSS rescore
  9. 2026-07-19 14:31 UTCEPSS rescore
  10. 2026-07-19 02:29 UTCEPSS rescore
  11. 2026-07-18 10:04 UTCEPSS rescore
  12. 2026-07-16 17:03 UTCEPSS rescore
  13. 2026-07-15 16:57 UTCEPSS rescore
  14. 2026-07-15 16:57 UTCEPSS rescore
  15. 2026-07-15 02:00 UTCEPSS rescore
  16. 2026-07-15 02:00 UTCEPSS rescore
  17. 2026-07-14 09:24 UTCEG score recompute▼ 1.70
  18. 2026-07-13 22:31 UTCEPSS rescore
  19. 2026-07-13 22:08 UTCNVD updateCVSS v3 → 5.4 · severity → MEDIUM
  20. 2026-07-13 06:13 UTCEPSS rescore
  21. 2026-07-13 06:13 UTCEPSS rescore
  22. 2026-07-12 05:46 UTCEPSS rescore
  23. 2026-07-10 20:38 UTCEG score recompute
  24. 2026-07-10 20:37 UTCMITRE cvelistV5first tracked

Related CVEs(same vendor + same CWE)

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 87.4% 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

Explore the affected products and dependency analysis for 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.

Start Free Scan →Browse All CVEs