CVE-2026-57215

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 69% 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 week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

A fix is available — apply it.

RabbitMQ is a messaging and streaming broker. Prior to 3.13.15, 4.0.20, 4.1.11, and 4.2.6, RabbitMQ allows foreign bindings to amq.rabbitmq.reply-to destinations because volatile direct-reply-to queues can be accepted at bind and route time but are missing from Khepri-backed deletion checks, leaving persistent route entries after unbind. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6.

CVSS v3
8.8
EG Score
8.8(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
Severity88% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
31%
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_commit, github_pr, github_release, github.
github Patch Available🟡 PoC Available

Direct-reply-to binding persistence can lead to unauthorized reply-channel injection and persistent phantom · Advisory · rabbitmq/rabbitmq-server · GitHub

https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-5cq3-v9jx-p3x3
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

Reject bindings to Direct Reply-to virtual "queues" (backport #15935) (backport #15937)

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

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

Reject bindings to Direct Reply-to virtual "queues"

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

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

commit c84f3c880e0f (rabbitmq/rabbitmq-server)

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

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

commit 9055500d10ca (rabbitmq/rabbitmq-server)

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

https://github.com/rabbitmq/rabbitmq-server/commit/9055500d10ca7629dd2b051c6dc7a4b0bb8f6734

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

Frequently asked(5)

What is CVE-2026-57215?
CVE-2026-57215 is a high vulnerability published on July 10, 2026. RabbitMQ is a messaging and streaming broker. Prior to 3.13.15, 4.0.20, 4.1.11, and 4.2.6, RabbitMQ allows foreign bindings to amq.rabbitmq.reply-to destinations because volatile direct-reply-to queues can be accepted at bind and route time but are missing from Khepri-backed deletion checks,…
When was CVE-2026-57215 disclosed?
CVE-2026-57215 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-57215 actively exploited?
CVE-2026-57215 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 69.0% of all scored CVEs.
What is the CVSS score of CVE-2026-57215?
CVE-2026-57215 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-57215?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-57215, 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-57215

Explore →

Is Your Infrastructure Affected by CVE-2026-57215?

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

Start Free Scan →Browse All CVEs