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.3%, top 81% 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 — 4 sources updated this weekElevated
6.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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)
EPSS
24.0%
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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 16× in last 7d / 16× 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-15 02:00 UTCEPSS rescore
  2. 2026-07-15 02:00 UTCEPSS rescore
  3. 2026-07-14 08:52 UTCEG score recompute▼ 0.50
  4. 2026-07-13 22:31 UTCEPSS rescore
  5. 2026-07-13 22:08 UTCNVD updateCVSS v3 → 6.5 · severity → MEDIUM
  6. 2026-07-13 20:48 UTCEG score recompute
  7. 2026-07-13 08:47 UTCEG score recompute
  8. 2026-07-13 06:13 UTCEPSS rescore
  9. 2026-07-13 06:13 UTCEPSS rescore
  10. 2026-07-12 20:46 UTCEG score recompute
  11. 2026-07-12 08:41 UTCEG score recompute
  12. 2026-07-12 05:46 UTCEPSS rescore
  13. 2026-07-11 20:40 UTCEG score recompute
  14. 2026-07-11 08:39 UTCEG score recompute
  15. 2026-07-10 20:38 UTCEG score recompute
  16. 2026-07-10 20:37 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

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 24.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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