CVE-2026-57220

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 65% 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, secondary
Trending — 3 sources updated this week
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 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 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.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
34.6%
KEV
Not listed

Published

July 10, 2026

Last Modified

July 10, 2026

Advisory Details (6)

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

Stream 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-j35q
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

Limit 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/16173
github_pr

Limit 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/16171
github_commit

commit 773a49c4921e (rabbitmq/rabbitmq-server)

Fix landed in rabbitmq/rabbitmq-server commit 773a49c4921e — awaiting tagged release

https://github.com/rabbitmq/rabbitmq-server/commit/773a49c4921e8be990262a2d609c35916825679e
github_commit

commit 595ec28fa162 (rabbitmq/rabbitmq-server)

Fix landed in rabbitmq/rabbitmq-server commit 595ec28fa162 — awaiting tagged release

https://github.com/rabbitmq/rabbitmq-server/commit/595ec28fa1621b1f2c28124e4e0466a8ad963547

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 10× 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-13 06:55 UTCEG score recompute
  2. 2026-07-13 06:13 UTCEPSS rescore
  3. 2026-07-13 06:13 UTCEPSS rescore
  4. 2026-07-12 19:15 UTCEG score recompute
  5. 2026-07-12 07:36 UTCEG score recompute
  6. 2026-07-12 05:46 UTCEPSS rescore
  7. 2026-07-11 19:57 UTCEG score recompute
  8. 2026-07-11 08:18 UTCEG score recompute
  9. 2026-07-10 20:39 UTCEG score recompute
  10. 2026-07-10 20:37 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-57220?
CVE-2026-57220 is a high vulnerability published on July 10, 2026. 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…
When was CVE-2026-57220 disclosed?
CVE-2026-57220 was first published in the National Vulnerability Database on July 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-57220 actively exploited?
CVE-2026-57220 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 34.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-57220?
CVE-2026-57220 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-57220?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-57220, 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-57220

Explore →

Is Your Infrastructure Affected by CVE-2026-57220?

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

Start Free Scan →Browse All CVEs