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.7%, top 50% 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: 1%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%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
50%
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

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.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
rabbitmq-server3.10.8-1 ... 4.3.2-4 (38 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
rabbitmq-server3.10.8-1.1 ... 4.3.2-4 (27 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
rabbitmq-server4.0.5-10 ... 4.3.2-4 (17 versions)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
rabbitmq-server4.0.5-10 ... 4.3.0-1 (9 versions)4.3.0-2

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 62× 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.

Showing the most recent 100 of 186 total refreshes for this CVE.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 05:17 UTCEG score recompute
  3. 2026-09-18 05:17 UTCVendor advisory
  4. 2026-09-17 19:31 UTCEPSS rescore
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-16 05:15 UTCEPSS rescore
  7. 2026-09-15 03:11 UTCEPSS rescore
  8. 2026-09-13 23:38 UTCEG score recompute
  9. 2026-09-13 23:38 UTCVendor advisory
  10. 2026-09-13 16:47 UTCEPSS rescore
  11. 2026-09-13 08:11 UTCEG score recompute
  12. 2026-09-13 08:11 UTCVendor advisory
  13. 2026-09-12 15:01 UTCVendor advisory
  14. 2026-09-12 02:49 UTCEG score recompute
  15. 2026-09-12 02:49 UTCVendor advisory
  16. 2026-09-11 14:53 UTCEPSS rescore
  17. 2026-09-10 09:35 UTCEPSS rescore
  18. 2026-09-08 22:01 UTCEPSS rescore
  19. 2026-09-08 02:45 UTCEG score recompute
  20. 2026-09-08 02:45 UTCVendor advisory
  21. 2026-09-07 16:01 UTCEPSS rescore
  22. 2026-09-06 13:56 UTCEG score recompute
  23. 2026-09-06 13:56 UTCVendor advisory
  24. 2026-09-06 13:47 UTCEPSS rescore
  25. 2026-09-05 21:40 UTCEG score recompute
Show 75 more
  1. 2026-09-05 21:40 UTCVendor advisory
  2. 2026-09-04 05:07 UTCEPSS rescore
  3. 2026-09-02 14:12 UTCEPSS rescore
  4. 2026-09-01 13:54 UTCEPSS rescore
  5. 2026-09-01 04:40 UTCEPSS rescore
  6. 2026-08-30 19:17 UTCEPSS rescore
  7. 2026-08-30 18:26 UTCVendor advisory
  8. 2026-08-30 06:14 UTCEG score recompute
  9. 2026-08-30 06:14 UTCVendor advisory
  10. 2026-08-30 01:22 UTCEPSS rescore
  11. 2026-08-28 21:42 UTCEPSS rescore
  12. 2026-08-27 21:40 UTCEG score recompute
  13. 2026-08-27 21:40 UTCVendor advisory
  14. 2026-08-27 14:25 UTCEPSS rescore
  15. 2026-08-27 00:46 UTCEG score recompute
  16. 2026-08-27 00:46 UTCVendor advisory
  17. 2026-08-26 14:46 UTCEPSS rescore
  18. 2026-08-26 03:32 UTCEG score recompute
  19. 2026-08-26 03:32 UTCVendor advisory
  20. 2026-08-25 13:49 UTCEPSS rescore
  21. 2026-08-25 09:49 UTCVendor advisory
  22. 2026-08-24 20:13 UTCEG score recompute
  23. 2026-08-24 20:13 UTCVendor advisory
  24. 2026-08-24 06:28 UTCVendor advisory
  25. 2026-08-23 17:52 UTCVendor advisory
  26. 2026-08-23 05:41 UTCEG score recompute
  27. 2026-08-23 05:41 UTCVendor advisory
  28. 2026-08-23 00:19 UTCEPSS rescore
  29. 2026-08-22 17:28 UTCVendor advisory
  30. 2026-08-22 04:42 UTCEG score recompute
  31. 2026-08-22 04:42 UTCVendor advisory
  32. 2026-08-21 23:49 UTCEPSS rescore
  33. 2026-08-21 16:04 UTCVendor advisory
  34. 2026-08-21 03:44 UTCEG score recompute
  35. 2026-08-21 03:44 UTCVendor advisory
  36. 2026-08-20 22:55 UTCEPSS rescore
  37. 2026-08-20 15:11 UTCVendor advisory
  38. 2026-08-20 01:32 UTCEG score recompute
  39. 2026-08-20 01:32 UTCVendor advisory
  40. 2026-08-19 17:04 UTCEPSS rescore
  41. 2026-08-19 12:17 UTCVendor advisory
  42. 2026-08-18 23:43 UTCEG score recompute
  43. 2026-08-18 23:43 UTCVendor advisory
  44. 2026-08-18 13:48 UTCEPSS rescore
  45. 2026-08-18 11:31 UTCVendor advisory
  46. 2026-08-17 23:20 UTCEG score recompute
  47. 2026-08-17 23:20 UTCVendor advisory
  48. 2026-08-17 13:47 UTCEPSS rescore
  49. 2026-08-17 11:08 UTCVendor advisory
  50. 2026-08-16 22:57 UTCEG score recompute
  51. 2026-08-16 22:57 UTCVendor advisory
  52. 2026-08-16 14:56 UTCEPSS rescore
  53. 2026-08-16 10:45 UTCEG score recompute
  54. 2026-08-16 10:45 UTCVendor advisory
  55. 2026-08-16 02:14 UTCEPSS rescore
  56. 2026-08-15 22:34 UTCVendor advisory
  57. 2026-08-15 10:22 UTCEG score recompute
  58. 2026-08-15 10:22 UTCVendor advisory
  59. 2026-08-15 01:30 UTCEPSS rescore
  60. 2026-08-14 22:10 UTCVendor advisory
  61. 2026-08-14 09:59 UTCEG score recompute
  62. 2026-08-14 09:59 UTCVendor advisory
  63. 2026-08-13 22:00 UTCEPSS rescore
  64. 2026-08-13 21:47 UTCVendor advisory
  65. 2026-08-13 09:36 UTCVendor advisory
  66. 2026-08-12 21:24 UTCEG score recompute
  67. 2026-08-12 21:24 UTCVendor advisory
  68. 2026-08-12 13:51 UTCEPSS rescore
  69. 2026-08-12 09:13 UTCVendor advisory
  70. 2026-08-11 21:02 UTCEG score recompute
  71. 2026-08-11 21:02 UTCVendor advisory
  72. 2026-08-11 08:51 UTCEG score recompute
  73. 2026-08-11 08:51 UTCVendor advisory
  74. 2026-08-11 00:00 UTCEPSS rescore
  75. 2026-08-10 20:39 UTCVendor advisory

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 1% probability of exploitation in the next 30 days, which ranks it in the top 50.3% 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

See which npm, PyPI, Go, and Maven packages are affected by 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.