CVE-2026-57217

MEDIUMNVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

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

A fix is available — apply it.

RabbitMQ is a messaging and streaming broker. Prior to 3.13.15, 4.0.21, 4.1.11, and 4.2.6, RabbitMQ topic authorization can allow restricted topic writes and binds during metadata-store failures because topic-permission lookup errors from Khepri can collapse to undefined, which the internal backend treats as allow. This issue is fixed in versions 3.13.15, 4.0.21, 4.1.11, and 4.2.6.

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

Published

July 10, 2026

Last Modified

July 13, 2026

Advisory Details (6)

Auto-updated Jul 10, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_pr, github_release.
github Patch Available🟡 PoC Available

Topic authorization can lead to cross-tenant routing-key bypass · Advisory · rabbitmq/rabbitmq-server · GitHub

https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-gpvw-75h5-3wvx
github_release Patch Available

RabbitMQ 4.2.6

Patch available: rabbitmq/rabbitmq-server v4.2.6

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

Khepri reads: distinguish missing keys from errors in one place (backport #15941) (backport #15942)

Fix merged in rabbitmq/rabbitmq-server PR #15943 on 2026-04-06 — awaiting tagged release

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

Khepri reads: distinguish missing keys from errors in one place

Fix merged in rabbitmq/rabbitmq-server PR #15941 on 2026-04-06 — awaiting tagged release

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

commit ce1f682aa6b3 (rabbitmq/rabbitmq-server)

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

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

commit 94f1d33a70fc (rabbitmq/rabbitmq-server)

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

https://github.com/rabbitmq/rabbitmq-server/commit/94f1d33a70fcfa09006649599e79fc92786a2d36

Vendor Advisories for CVE-2026-57217(1)

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.

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-57217?
CVE-2026-57217 is a medium vulnerability published on July 10, 2026. RabbitMQ is a messaging and streaming broker. Prior to 3.13.15, 4.0.21, 4.1.11, and 4.2.6, RabbitMQ topic authorization can allow restricted topic writes and binds during metadata-store failures because topic-permission lookup errors from Khepri can collapse to undefined, which the internal backend…
When was CVE-2026-57217 disclosed?
CVE-2026-57217 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-57217 actively exploited?
CVE-2026-57217 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 72.1% of all scored CVEs.
What is the CVSS score of CVE-2026-57217?
CVE-2026-57217 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-57217?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-57217, 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-57217

Explore →

Is Your Infrastructure Affected by CVE-2026-57217?

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

Start Free Scan →Browse All CVEs