CVE-2026-57221

MEDIUMNVD 5.05.0—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.0 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 81% 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 — 4 sources updated this week
5.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.0Exploit: 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 3.13.15, 4.0.20, 4.1.11, and 4.2.6, RabbitMQ does not perform authorization checks on passive queue.declare and exchange.declare AMQP 0-9-1 operations, allowing any authenticated user who can connect to a virtual host to enumerate queue and exchange names and read queue message and consumer counts. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6.

CVSS v3
5.0
EG Score
5.0(medium)
EPSS
19.0%
KEV
Not listed

Published

July 10, 2026

Last Modified

July 13, 2026

Advisory Details (6)

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

Passive queue/exchange declaration bypasses authorization checks, leaking queue metadata to unprivileged users · Advisory · rabbitmq/rabbitmq-server · GitHub

https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-9q2j-2hq8-22r2
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

AMQP 0-9-1: apply `configure` checks to passive queue, exchange declarations (backport #16085) (backport #16088)

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

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

AMQP 0-9-1: apply `configure` checks to passive queue, exchange declarations

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

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

commit dc3d1aa4f5c3 (rabbitmq/rabbitmq-server)

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

https://github.com/rabbitmq/rabbitmq-server/commit/dc3d1aa4f5c3331a425ee599b45be9423a2e83fc
github_commit

commit 709a14e49e06 (rabbitmq/rabbitmq-server)

Fix landed in rabbitmq/rabbitmq-server commit 709a14e49e06 — awaiting tagged release

https://github.com/rabbitmq/rabbitmq-server/commit/709a14e49e06c138a8cd672c9809ca34a2767962

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 16× in last 7d / 16× 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-16 01:31 UTCEG score recompute
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-15 16:57 UTCEPSS rescore
  4. 2026-07-15 02:00 UTCEPSS rescore
  5. 2026-07-15 02:00 UTCEPSS rescore
  6. 2026-07-15 00:33 UTCEG score recompute
  7. 2026-07-13 23:32 UTCEG score recompute▼ 0.30
  8. 2026-07-13 22:31 UTCEPSS rescore
  9. 2026-07-13 22:08 UTCNVD updateCVSS v3 → 5
  10. 2026-07-13 06:13 UTCEPSS rescore
  11. 2026-07-13 06:13 UTCEPSS rescore
  12. 2026-07-12 22:34 UTCEG score recompute
  13. 2026-07-12 05:46 UTCEPSS rescore
  14. 2026-07-11 21:36 UTCEG score recompute
  15. 2026-07-10 20:38 UTCEG score recompute
  16. 2026-07-10 20:37 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-57221?
CVE-2026-57221 is a medium 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, RabbitMQ does not perform authorization checks on passive queue.declare and exchange.declare AMQP 0-9-1 operations, allowing any authenticated user who can connect to a virtual host to enumerate queue and…
When was CVE-2026-57221 disclosed?
CVE-2026-57221 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-57221 actively exploited?
CVE-2026-57221 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 19.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-57221?
CVE-2026-57221 has a CVSS v3 base score of 5.0 (NVD).
How do I remediate CVE-2026-57221?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-57221, 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-57221

Explore →

Is Your Infrastructure Affected by CVE-2026-57221?

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

Start Free Scan →Browse All CVEs