CVE-2026-57221: RabbitMQ: Passive queue/exchange declaration bypasses authorization checks, leaking queue metadata to unprivileged users
Noroxi assessment
Priority: Monitor (action score 21/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.41% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: rabbitmq-server (Debian:14) 4.3.0-2; rabbitmq-server (openSUSE:Leap 16.0) 4.1.5-160000.2.1; rabbitmq-server4.2 (Red Hat:hummingbird:1) 0:4.2.8-1.hum1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to rabbitmq-server (Debian:14) 4.3.0-2; rabbitmq-server (openSUSE:Leap 16.0) 4.1.5-160000.2.1; rabbitmq-server4.2 (Red Hat:hummingbird:1) 0:4.2.8-1.hum1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jul 10, 2026
- Updated
- Oct 25, 2026
- EPSS
- 0.4% · 35th percentile
- CWE
- CWE-862
Report tools
Action score
21
Monitor
Low priority for now.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 5.3
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| broadcom | rabbitmq server | cpe:2.3:a:broadcom:rabbitmq_server |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- broadcom rabbitmq server3.13.0 and later · before 4.2.6
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
rabbitmq rabbitmq-server
- >= 4.2.0, < 4.2.6, >= 4.1.0, < 4.1.11, >= 4.0.0, < 4.0.21, >= 3.13.0, < 3.13.15affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | rabbitmq-server | from 0 | — |
| Debian:14 | rabbitmq-server | before 4.3.0-2 | 4.3.0-2 |
| openSUSE:Leap 16.0 | rabbitmq-server | before 4.1.5-160000.2.1 | 4.1.5-160000.2.1 |
| Red Hat:hummingbird:1 | rabbitmq-server4.2 | before 0:4.2.8-1.hum1 | 0:4.2.8-1.hum1 |
| Red Hat:hummingbird:1 | rabbitmq-server4.3 | before 0:4.3.2-1.hum1 | 0:4.3.2-1.hum1 |
| SUSE:Linux Enterprise Server 16.0 | rabbitmq-server | before 4.1.5-160000.2.1 | 4.1.5-160000.2.1 |
Same product
broadcom: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-57216RabbitMQ: AMQP 1.0, AMQP 0-9-1, Stream Protocol loopback enforcement can lead to remote guest sessions due to listener-address loopback checks40Plan
- CVE-2026-57211RabbitMQ: UNC SSRF affecting the management UI on Windows40Plan
- CVE-2016-9877An issue was discovered in Pivotal RabbitMQ 3.x before 3.5.8 and 3.6.x before 3.6.6 and RabbitMQ for PCF 1.5.x before 1.5.20, 1.6.x before 139Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-57219Jul 10, 2026 · RabbitMQ: Unauthenticated disclosure of OAuth client credentials via an HTTP API endpoint with certain less common OAuth 2 configurations35Monitor
- ← EarlierCVE-2026-57220Jul 10, 2026 · RabbitMQ: Stream listener does not enforce configured frame-size limit during authentication, permitting unauth'd mem-exhaust DoS30Monitor
- Later →CVE-2026-66070Sep 23, 2026 · RabbitMQ: CORS * reflects Origin with Allow-Credentials30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:rabbitmq-server | 4.3.0-2 · Debian:14 | Package registry (OSV) |
| opensuse:rabbitmq-server | 4.1.5-160000.2.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| red hat:rabbitmq-server4.2 | 0:4.2.8-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:rabbitmq-server4.3 | 0:4.3.2-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| suse:rabbitmq-server | 4.1.5-160000.2.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-6723376 days apartRabbitMQ: Monitoring-tag user can DELETE shovels24Monitor
- CVE-2026-6741277 days apartRabbitMQ: Federation upstream skips vhost authorization allowing cross-vhost message access24Monitor
- CVE-2026-6740777 days apartRabbitMQ: Incomplete fix for CVE-2026-44838: `escape_regex_char/1` does not escape `-`, leaving room for an MQTT topic permission bypass20Monitor
- CVE-2026-6724177 days apartRabbitMQ: AMQP 1.0 management exchange.declare skips alternate-exchange permission check19Monitor
- CVE-2026-6742177 days apartRabbitMQ: Stored HTML Injection in RabbitMQ Management OAuth Error Handling18Monitor
- CVE-2026-6607675 days apartRabbitMQ: Cross-vhost quorum-queue status and stream tracking disclosure9Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0532 · Jul 13, 2026(RabbitMQ Güvenlik Zafiyeti)
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-862 · Missing AuthorizationCVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.