CVE-2026-57217

MEDIUMNVD 6.56.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.4% (26th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Elevated
6.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 6.5Exploit: No code on recordExposed services: Not assessed

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.5MEDIUMmedium confidence
EG Risk
45
EG Risk 45/100

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 (value × EchelonGraph’s weight)
Severity65% × 45%
The EG Score, 6.5 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
26th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 10, 2026

Last Modified

July 13, 2026

Advisory Details (6)

Auto-updated Jul 10, 2026
Patch available. Sources: github, github_commit, github_pr, github_release.
GitHub advisoryMentions a patch (unverified)

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 pull request

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 pull request

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(3)

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 / EcosystemFix (by version range) / 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 rangeFix by version rangeDependents
rabbitmq-server3.10.8-1 ... 4.3.2-4 (38 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
rabbitmq-server3.10.8-1.1 ... 4.3.2-5 (28 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
rabbitmq-server4.0.5-10 ... 4.3.2-5 (18 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
rabbitmq-server4.0.5-10 ... 4.3.0-1 (9 versions)
  • every version up to 4.3.0-2: fixed in 4.3.0-2
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 40× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 185 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 85 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-57217?
CVE-2026-57217 is a medium-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-57217 published?
The CVE record for CVE-2026-57217 was published on July 10, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 13, 2026; the record at its source may have been updated since.
Is CVE-2026-57217 actively exploited?
CVE-2026-57217 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (26th percentile of EPSS-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?
A fix for CVE-2026-57217 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-57217 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Book a Demo →Browse All CVEs