NVD / CVE Program· CNA GitHub_M

CVE-2026-57216: RabbitMQ: AMQP 1.0, AMQP 0-9-1, Stream Protocol loopback enforcement can lead to remote guest sessions due to listener-address loopback checks

Noroxi assessment

Priority: Plan (action score 40/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.50% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
Fixed version: azl3 rabbitmq-server 3.13.7-6 on Azure Linux 3.0 3.13.7-7.
Severity is disputed: the assigning authority (CNA) scores it 6.8, NVD 10.0.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Add it to your regular patch cycle. Upgrade to azl3 rabbitmq-server 3.13.7-6 on Azure Linux 3.0 3.13.7-7 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, AMQP 0-9-1, AMQP 1.0, and Stream Protocol authentication can allow a loopback-restricted user such as guest to connect remotely when traffic is accepted through a trusted PROXY-protocol path and the backend listener is loopback-bound because the loopback check uses the listener-side socket address instead of the real client source. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6.

CriticalCVSS 10.0 · v3.1—No exploit Fix available

Published: Jul 10, 2026
Updated: Oct 25, 2026
EPSS: 0.5% · 43th percentile
CWE: CWE-287

Report tools

JSON

Action score

Plan

Add it to your regular patch cycle.

CVSS: 40 / 40 · 10.0 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.5%

CISA SSVC decision

Exploitation: proof of concept
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 10.0
CNA · GitHub_M: 6.8; 3.2 point gap

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A: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

Is your version affected? Check it

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 help

Affected 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 3.13.15
broadcom rabbitmq server4.0.0 and later · before 4.0.20
broadcom rabbitmq server4.1.0 and later · before 4.1.11
broadcom rabbitmq server4.2.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 records

Other highest-scoring records for the same primary product.

CVE-2026-57211RabbitMQ: UNC SSRF affecting the management UI on Windows
40Plan
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 1
39Monitor
CVE-2026-67404RabbitMQ: OAuth2 silent verify_none fallback for JWKS fetch
36Monitor

Published before and after this one in the same product

← EarlierCVE-2026-57214Jul 10, 2026 · RabbitMQ: Stored XSS in RabbitMQ management UI
28Monitor
← EarlierCVE-2026-57215Jul 10, 2026 · RabbitMQ: Direct-reply-to binding persistence can lead to unauthorized reply-channel injection and persistent phantom
28Monitor
Later →CVE-2026-57217Jul 10, 2026 · RabbitMQ: Topic authorization can lead to cross-tenant routing-key bypass
28Monitor

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
azl3 rabbitmq-server 3.13.7-6 on Azure Linux 3.0	3.13.7-7 · CBL-Mariner Releases	Microsoft (MSRC)
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.

No history yet (it accumulates with the daily EPSS job).

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 researchers

Finders, 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.

—

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

CVE-2026-6722475 days apartRabbitMQ: Admin path-traversal write via trace name
8Monitor

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)

All national notices →

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Impact can extend beyond the vulnerable component (scope changes).

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Changed
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-287 · Improper Authentication

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

nvd-primary

Root cause

Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.

The bug in code

The whole CWE-287 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1app.use("/admin", requireSession, adminRouter);
2

3// Route added later skips the middleware
4app.post("/admin-api/config", updateConfig);

Fixed

1const admin = express.Router();
2admin.use(requireSession, requireRole("admin"));
3

4admin.post("/config", updateConfig);
5app.use("/admin", admin);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

Change log

Fix✗ → ✓Sep 28, 2026, 10:45 PM UTC

For records you follow, these changes also arrive as notifications. →

References

github.com/rabbitmq/rabbitmq-server/commit/7273c9eb6920abcde17b892dbe97ccaf906ead47

Show all references (4 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records