CVE-2026-57216

CRITICALNVD 10.010.0—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 10.0 under NVD CVSS v3. EPSS exploit probability: 0.9%, top 44% 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 weekElevated
10.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 10.0Exploit: Elevated riskExposed: 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, AMQP 0-9-1, AMQP 1.0, and Stream Protocol authentication can allow a loopback-restricted user such as guest to connect remotely when traffic is accepted through a trusted PROXY-protocol path and the backend listener is loopback-bound because the loopback check uses the listener-side socket address instead of the real client source. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6.

CVSS v3
10.0
EG Score
10.0(medium)
EG Risk
61(Track)
EG Risk 61/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
Severity100% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
56%
KEV
Not listed

Published

July 10, 2026

Last Modified

July 13, 2026

Advisory Details (6)

Auto-updated Aug 25, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available🟡 PoC Available

AMQP 1.0, AMQP 0-9-1, Stream Protocol loopback enforcement can lead to remote guest sessions due to listener-address loopback checks · Advisory · rabbitmq/rabbitmq-server · GitHub

https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-36m6-588r-vqcw
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

Use `peername/1` over `sockname/1` in a few places (backport #15936) (backport #15939)

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

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

Use `peername/1` over `sockname/1` in a few places

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

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

commit 9f8c39fcf0ac (rabbitmq/rabbitmq-server)

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

https://github.com/rabbitmq/rabbitmq-server/commit/9f8c39fcf0acbc43080ee7017a62a02832114112
github_commit

commit 7273c9eb6920 (rabbitmq/rabbitmq-server)

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

https://github.com/rabbitmq/rabbitmq-server/commit/7273c9eb6920abcde17b892dbe97ccaf906ead47

Vendor Advisories for CVE-2026-57216(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 / 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 30× in last 7d / 185× 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 252 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-57216?
CVE-2026-57216 is a critical 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, AMQP 0-9-1, AMQP 1.0, and Stream Protocol authentication can allow a loopback-restricted user such as guest to connect remotely when traffic is accepted through a trusted PROXY-protocol path and the backend…
When was CVE-2026-57216 disclosed?
CVE-2026-57216 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-57216 actively exploited?
CVE-2026-57216 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 43.7% of all scored CVEs.
What is the CVSS score of CVE-2026-57216?
CVE-2026-57216 has a CVSS v3 base score of 10.0 (NVD).
How do I remediate CVE-2026-57216?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-57216, 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-57216

Explore →

Is Your Infrastructure Affected by CVE-2026-57216?

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

Start Free Scan →Browse All CVEs