RabbitMQ is a messaging and streaming broker. Prior to 4.2.6, RabbitMQ AMQP 0-9-1 allows an existing consumer to keep receiving messages after OAuth token expiry or connection.update_secret refresh to reduced scopes because existing consumers are not canceled or reauthorized at delivery time after the channel user state changes. This issue is fixed in version 4.2.6.
CVE-2026-57218
MEDIUMNVD 6.56.5—Trending — 4 sources updated this weekElevated
EchelonGraph scoreMEDIUM confidence
This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 76% 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
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.
- CVSS v3
- 6.5
- EG Score
- 6.5(medium)
- EPSS
- 24.1%
- 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_release, github, github_commit, github_pr.
github Patch Available🟡 PoC Available
AMQP 0-9-1 in combination with OAuth 2: consumer persistence can lead to post-revocation message disclosure · Advisory · rabbitmq/rabbitmq-server · GitHub
https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-wmrr-4h5v-5ch7github_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.6github_pr
AMQP 0-9-1: clear permissions cache and re-validate consumer permissions immediately when the connection secret changes (backport #16092) (backport #16093)
Fix merged in rabbitmq/rabbitmq-server PR #16097 on 2026-04-15 — awaiting tagged release
https://github.com/rabbitmq/rabbitmq-server/pull/16097github_pr
AMQP 0-9-1: clear permissions cache and re-validate consumer permissions immediately when the connection secret changes
Fix merged in rabbitmq/rabbitmq-server PR #16092 on 2026-04-14 — awaiting tagged release
https://github.com/rabbitmq/rabbitmq-server/pull/16092github_commit
commit db20d6c0fcf3 (rabbitmq/rabbitmq-server)
Fix landed in rabbitmq/rabbitmq-server commit db20d6c0fcf3 — awaiting tagged release
https://github.com/rabbitmq/rabbitmq-server/commit/db20d6c0fcf3056030f244b5adab0d45c0db0c9egithub_commit
commit 501ad947cd6b (rabbitmq/rabbitmq-server)
Fix landed in rabbitmq/rabbitmq-server commit 501ad947cd6b — awaiting tagged release
https://github.com/rabbitmq/rabbitmq-server/commit/501ad947cd6bbcc9486fe96e0d073992bfe52cc4Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 13× in last 7d / 13× 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.
- 2026-07-15 03:55 UTCEG score recompute
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-14 02:06 UTCEG score recompute▲ 1.60
- 2026-07-13 22:31 UTCEPSS rescore
- 2026-07-13 22:08 UTCNVD updateCVSS v3 → 6.5
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 00:17 UTCEG score recompute
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 22:28 UTCEG score recompute
- 2026-07-10 20:38 UTCEG score recompute
- 2026-07-10 20:37 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-863
Frequently asked(5)
What is CVE-2026-57218?
CVE-2026-57218 is a medium vulnerability published on July 10, 2026. RabbitMQ is a messaging and streaming broker. Prior to 4.2.6, RabbitMQ AMQP 0-9-1 allows an existing consumer to keep receiving messages after OAuth token expiry or connection.update_secret refresh to reduced scopes because existing consumers are not canceled or reauthorized at delivery time after…
When was CVE-2026-57218 disclosed?
CVE-2026-57218 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-57218 actively exploited?
CVE-2026-57218 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 24.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-57218?
CVE-2026-57218 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-57218?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-57218, 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-57218
Is Your Infrastructure Affected by CVE-2026-57218?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.