RabbitMQ is a messaging and streaming broker. Prior to 4.2.6, the RabbitMQ stream listener does not enforce the configured stream frame-size limit while assembling frames during authentication and before Tune negotiation, allowing an unauthenticated remote client to declare oversized frame lengths and consume broker memory in rabbit_stream_core. This issue is fixed in version 4.2.6.
CVE-2026-57220
This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 1.0%, top 41% 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).
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EG Risk
- 65(Attend)EG Risk 65/100SSVC: Attend
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 computedSeverity75% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 1%
- EPSS %ILE
- 59%
- KEV
- Not listed
Published
July 10, 2026
Last Modified
July 13, 2026
Advisory Details (6)
Auto-updated Jul 10, 2026Stream listener does not enforce configured frame-size limit during authentication, permitting unauth'd mem-exhaust DoS · Advisory · rabbitmq/rabbitmq-server · GitHub
https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-f364-87q5-j35qRabbitMQ 4.2.6
Patch available: rabbitmq/rabbitmq-server v4.2.6
https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.6Limit heap size for unauthenticated connections (backport #16171) (backport #16172)
Fix merged in rabbitmq/rabbitmq-server PR #16173 on 2026-04-16 — awaiting tagged release
https://github.com/rabbitmq/rabbitmq-server/pull/16173Limit heap size for unauthenticated connections
Fix merged in rabbitmq/rabbitmq-server PR #16171 on 2026-04-16 — awaiting tagged release
https://github.com/rabbitmq/rabbitmq-server/pull/16171commit 773a49c4921e (rabbitmq/rabbitmq-server)
Fix landed in rabbitmq/rabbitmq-server commit 773a49c4921e — awaiting tagged release
https://github.com/rabbitmq/rabbitmq-server/commit/773a49c4921e8be990262a2d609c35916825679ecommit 595ec28fa162 (rabbitmq/rabbitmq-server)
Fix landed in rabbitmq/rabbitmq-server commit 595ec28fa162 — awaiting tagged release
https://github.com/rabbitmq/rabbitmq-server/commit/595ec28fa1621b1f2c28124e4e0466a8ad963547Vendor Advisories for CVE-2026-57220(3)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- CVE-2026-57220Microsoft Security Response Center (MSRC)High
RabbitMQ: Stream listener does not enforce configured frame-size limit during authentication, permitting unauth'd mem-exhaust DoS
- RHSA-2026:35940Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
- RHSA-2026:35939Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
Patch Availability(2)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | rabbitmq-server4-3-main-4.3.2-1.hum1 | 2026-07-06 | redhat |
| redhat | rabbitmq-server4-2-main-4.2.8-1.hum1 | 2026-07-06 | redhat |
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.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 18× in last 7d / 108× 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 154 total refreshes for this CVE.
- 2026-08-30 06:14 UTCEG score recompute
- 2026-08-30 06:14 UTCVendor advisory
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-27 21:40 UTCEG score recompute
- 2026-08-27 21:40 UTCVendor advisory
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-27 00:46 UTCEG score recompute
- 2026-08-27 00:46 UTCVendor advisory
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-26 03:32 UTCEG score recompute
- 2026-08-26 03:32 UTCVendor advisory
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 07:52 UTCVendor advisory
- 2026-08-24 20:13 UTCEG score recompute
- 2026-08-24 20:13 UTCVendor advisory
- 2026-08-24 03:56 UTCVendor advisory
- 2026-08-23 14:29 UTCVendor advisory
- 2026-08-23 02:50 UTCEG score recompute
- 2026-08-23 02:50 UTCVendor advisory
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 15:10 UTCVendor advisory
- 2026-08-22 03:31 UTCEG score recompute
- 2026-08-22 03:31 UTCVendor advisory
- 2026-08-21 23:49 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-08-21 14:42 UTCVendor advisory
- 2026-08-21 03:02 UTCEG score recompute
- 2026-08-21 03:02 UTCVendor advisory
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 15:11 UTCVendor advisory
- 2026-08-20 01:32 UTCEG score recompute
- 2026-08-20 01:32 UTCVendor advisory
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 10:16 UTCVendor advisory
- 2026-08-18 22:31 UTCEG score recompute
- 2026-08-18 22:31 UTCVendor advisory
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-18 10:52 UTCVendor advisory
- 2026-08-17 23:13 UTCEG score recompute
- 2026-08-17 23:13 UTCVendor advisory
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 11:25 UTCVendor advisory
- 2026-08-16 23:46 UTCEG score recompute
- 2026-08-16 23:46 UTCVendor advisory
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 12:06 UTCEG score recompute
- 2026-08-16 12:06 UTCVendor advisory
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-16 00:28 UTCVendor advisory
- 2026-08-15 12:49 UTCEG score recompute
- 2026-08-15 12:49 UTCVendor advisory
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-15 01:08 UTCVendor advisory
- 2026-08-14 13:29 UTCVendor advisory
- 2026-08-14 01:48 UTCEG score recompute
- 2026-08-14 01:48 UTCVendor advisory
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 14:09 UTCVendor advisory
- 2026-08-13 02:31 UTCVendor advisory
- 2026-08-12 14:52 UTCEG score recompute
- 2026-08-12 14:52 UTCVendor advisory
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 03:13 UTCVendor advisory
- 2026-08-11 15:34 UTCEG score recompute
- 2026-08-11 15:34 UTCVendor advisory
- 2026-08-11 03:54 UTCEG score recompute
- 2026-08-11 03:54 UTCVendor advisory
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 16:16 UTCVendor advisory
- 2026-08-10 03:59 UTCVendor advisory
- 2026-08-09 16:20 UTCEG score recompute
- 2026-08-09 16:20 UTCVendor advisory
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 04:42 UTCVendor advisory
- 2026-08-08 17:03 UTCEG score recompute
- 2026-08-08 17:03 UTCVendor advisory
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 05:24 UTCVendor advisory
- 2026-08-07 17:45 UTCEG score recompute
- 2026-08-07 17:45 UTCVendor advisory
- 2026-08-07 06:06 UTCVendor advisory
- 2026-08-06 18:27 UTCEG score recompute
- 2026-08-06 18:27 UTCVendor advisory
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-06 06:48 UTCEG score recompute
- 2026-08-06 06:48 UTCVendor advisory
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 19:09 UTCVendor advisory
- 2026-08-05 07:30 UTCVendor advisory
- 2026-08-04 19:43 UTCEG score recompute
- 2026-08-04 19:43 UTCVendor advisory
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 10:39 UTCEPSS rescore
- 2026-08-04 08:04 UTCVendor advisory
- 2026-08-03 20:11 UTCEG score recompute
- 2026-08-03 20:11 UTCVendor advisory
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-03 08:32 UTCVendor advisory
- 2026-08-02 20:53 UTCVendor advisory
- 2026-08-02 09:14 UTCEG score recompute
Frequently asked(5)
What is CVE-2026-57220?
When was CVE-2026-57220 disclosed?
Is CVE-2026-57220 actively exploited?
What is the CVSS score of CVE-2026-57220?
How do I remediate CVE-2026-57220?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-57220
Is Your Infrastructure Affected by CVE-2026-57220?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.