CVE-2026-57218: RabbitMQ: AMQP 0-9-1 in combination with OAuth 2: consumer persistence can lead to post-revocation message disclosure
Noroxi assessment
Priority: Monitor (action score 19/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.35% (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 rabbitmq-server 4.2.6.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to rabbitmq rabbitmq-server 4.2.6 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 4.2.6, RabbitMQ AMQP 0-9-1 allows an existing consumer to keep receiving messages after OAuth token expiry or connection.update_secret refresh to reduced scopes because existing consumers are not canceled or reauthorized at delivery time after the channel user state changes. This issue is fixed in version 4.2.6.
- Published
- Jul 10, 2026
- Updated
- Oct 25, 2026
- EPSS
- 0.3% · 29th percentile
- CWE
- CWE-863
Report tools
Action score
19
Low priority for now.
- CVSS
- 19 / 40 · 4.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 4.9
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/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.
Is your version affected? Check itNoroxi 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 |
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.6affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- broadcom rabbitmq server4.2.0 and later · before 4.2.6
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| 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…39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-57215Jul 10, 2026 · RabbitMQ: Direct-reply-to binding persistence can lead to unauthorized reply-channel injection and persistent phantom28Monitor
- ← EarlierCVE-2026-57217Jul 10, 2026 · RabbitMQ: Topic authorization can lead to cross-tenant routing-key bypass28Monitor
- Later →CVE-2026-57219Jul 10, 2026 · RabbitMQ: Unauthenticated disclosure of OAuth client credentials via an HTTP API endpoint with certain less common OAuth 2 configurations35Monitor
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 |
|---|---|---|
| rabbitmq rabbitmq-server | 4.2.6 · description | Vendor (CNA) |
| 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.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-572150 days apartRabbitMQ: Direct-reply-to binding persistence can lead to unauthorized reply-channel injection and persistent phantom28Monitor
- CVE-2026-572170 days apartRabbitMQ: Topic authorization can lead to cross-tenant routing-key bypass28Monitor
- CVE-2026-6741177 days apartRabbitMQ: Web MQTT with PROXY Protocol enabled: a loopback-only user permission bypass24Monitor
- CVE-2026-4483844 days apartRabbitMQ MQTT Topic Permission Authorization Bypass21Monitor
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)
Not on record for this CVE: EPSS history · researcher credit · public bounty program.
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-863 · Incorrect AuthorizationCVSS vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- 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.