CVE-2026-57216

CRITICALNVD 10.010.0
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 10.0 under NVD CVSS v3. EPSS exploit probability: 0.5% (43rd 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
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-43019 (ENISA EUVD)Source: ENISA EUVD

10.0EG
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.5%CVSS: 10.0Exploit: 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.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.0CRITICALmedium confidence
EG Risk
61
EG Risk 61/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity100% × 45%
Impact severity (EG Severity): CVSS 10.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
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.5%
EPSS %ILE
43rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (10.0): severity, escalated by confirmed exploitation. This CVE's 10.0 is its impact severity (EG Severity), not escalated.

EG Severity
10.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

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.

The score's inputs: 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

October 25, 2026

Advisory Details (6)

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

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

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

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 / 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.6-1 (29 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
rabbitmq-server4.0.5-10 ... 4.3.6-1 (19 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 23× in last 7d / 81× 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 395 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 295 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

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

Frequently asked(5)

What is CVE-2026-57216?
CVE-2026-57216 is a critical-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.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 the CVE record for CVE-2026-57216 published?
The CVE record for CVE-2026-57216 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 October 25, 2026; the record at its source may have been updated since.
Is CVE-2026-57216 actively exploited?
CVE-2026-57216 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (43rd percentile of EPSS-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?
A fix for CVE-2026-57216 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-57216 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-57216

Explore →

Is Your Infrastructure Affected by CVE-2026-57216?

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

Book a Demo →Browse All CVEs