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.5%, top 60% 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

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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
40%
KEV
Not listed

Published

July 10, 2026

Last Modified

July 13, 2026

Advisory Details (6)

Auto-updated Jul 27, 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(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 46× in last 7d / 70× 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-31 18:05 UTCVendor advisory
  2. 2026-07-31 14:06 UTCVendor advisory
  3. 2026-07-31 10:00 UTCVendor advisory
  4. 2026-07-31 05:46 UTCVendor advisory
  5. 2026-07-31 01:47 UTCVendor advisory
  6. 2026-07-30 17:12 UTCEG score recompute
  7. 2026-07-30 17:12 UTCVendor advisory
  8. 2026-07-30 16:28 UTCEPSS rescore
  9. 2026-07-30 13:12 UTCEG score recompute
  10. 2026-07-30 13:12 UTCVendor advisory
  11. 2026-07-30 09:10 UTCVendor advisory
  12. 2026-07-30 05:10 UTCEG score recompute
  13. 2026-07-30 05:10 UTCVendor advisory
  14. 2026-07-30 01:30 UTCEPSS rescore
  15. 2026-07-30 01:30 UTCEPSS rescore
  16. 2026-07-30 01:11 UTCVendor advisory
  17. 2026-07-29 21:12 UTCVendor advisory
  18. 2026-07-29 17:11 UTCVendor advisory
  19. 2026-07-29 13:12 UTCVendor advisory
  20. 2026-07-29 09:12 UTCVendor advisory
  21. 2026-07-29 05:12 UTCVendor advisory
  22. 2026-07-29 01:12 UTCVendor advisory
  23. 2026-07-28 21:13 UTCVendor advisory
  24. 2026-07-28 17:13 UTCEG score recompute
  25. 2026-07-28 17:13 UTCVendor advisory
Show 45 more
  1. 2026-07-28 15:37 UTCEPSS rescore
  2. 2026-07-28 12:51 UTCVendor advisory
  3. 2026-07-28 08:52 UTCVendor advisory
  4. 2026-07-28 04:52 UTCVendor advisory
  5. 2026-07-28 00:52 UTCVendor advisory
  6. 2026-07-27 20:53 UTCVendor advisory
  7. 2026-07-27 16:46 UTCEG score recompute
  8. 2026-07-27 16:46 UTCVendor advisory
  9. 2026-07-27 14:14 UTCEPSS rescore
  10. 2026-07-27 08:19 UTCVendor advisory
  11. 2026-07-27 04:20 UTCVendor advisory
  12. 2026-07-27 00:12 UTCVendor advisory
  13. 2026-07-26 20:11 UTCVendor advisory
  14. 2026-07-26 16:12 UTCEG score recompute
  15. 2026-07-26 16:12 UTCVendor advisory
  16. 2026-07-26 14:54 UTCEPSS rescore
  17. 2026-07-26 14:54 UTCEPSS rescore
  18. 2026-07-26 12:08 UTCEG score recompute
  19. 2026-07-26 12:08 UTCVendor advisory
  20. 2026-07-25 14:18 UTCEPSS rescore
  21. 2026-07-25 14:18 UTCEPSS rescore
  22. 2026-07-24 14:18 UTCEPSS rescore
  23. 2026-07-24 14:18 UTCEPSS rescore
  24. 2026-07-23 14:18 UTCEPSS rescore
  25. 2026-07-23 03:20 UTCEG score recompute
  26. 2026-07-22 14:08 UTCEPSS rescore
  27. 2026-07-21 15:25 UTCEPSS rescore
  28. 2026-07-20 17:08 UTCEPSS rescore
  29. 2026-07-19 14:31 UTCEPSS rescore
  30. 2026-07-19 14:31 UTCEPSS rescore
  31. 2026-07-19 02:29 UTCEPSS rescore
  32. 2026-07-18 10:04 UTCEPSS rescore
  33. 2026-07-16 17:03 UTCEPSS rescore
  34. 2026-07-15 16:57 UTCEPSS rescore
  35. 2026-07-15 16:57 UTCEPSS rescore
  36. 2026-07-15 02:00 UTCEPSS rescore
  37. 2026-07-15 02:00 UTCEPSS rescore
  38. 2026-07-14 14:20 UTCEG score recompute▲ 3.20
  39. 2026-07-13 22:31 UTCEPSS rescore
  40. 2026-07-13 22:08 UTCNVD updateCVSS v3 → 10 · severity → CRITICAL
  41. 2026-07-13 06:13 UTCEPSS rescore
  42. 2026-07-13 06:13 UTCEPSS rescore
  43. 2026-07-12 05:46 UTCEPSS rescore
  44. 2026-07-10 20:39 UTCEG score recompute
  45. 2026-07-10 20:37 UTCMITRE cvelistV5first tracked

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 59.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

Explore the affected products and dependency analysis for 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