CVE-2026-57216

Description

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.

Severity
MEDIUM
CVSS v3
6.8
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N · source cna
Exploit chance (EPSS)
0.504%
chance of exploitation in the next 30 days
higher than 43.7% of scored CVEs · 2026-11-17
CISA KEV
Not listed
Public exploit code
Yes
Exploit references (NVD and CNA): 1
Metasploit modules: 0
Nuclei templates: 0

Weakness

CISA SSVC decision points

Exploitationpoc
Automatableno
Technical impactpartial
Scored2026-07-13

Timeline

  1. 2026-07-10Published by the CNA20:20 UTC
  2. 2026-07-13CISA SSVC decision recorded3 days after publication

The timeline shows what already happened. To be told when this CVE changes next, watch it from the API.

Affected products

Products listed as vulnerable. Upgrade to the version under "Fixed in", or a later one.

ProductVulnerable versionsFixed in
broadcom rabbitmq_serverfrom 3.13.0 before 3.13.15fixed in 3.13.15from 4.0.0 before 4.0.20fixed in 4.0.20from 4.1.0 before 4.1.11fixed in 4.1.11from 4.2.0 before 4.2.6fixed in 4.2.63.13.154.0.204.1.114.2.6

Products and versions as NVD and the vendor that published the CVE list them.

References

Get more CVE data from the API.

Free without a key or signup. Pro adds monitoring and higher limits: pricing.

Sources