Patch Forecast
Yellow warning
Plan into this sprint.

CVE-2026-67411

RabbitMQ is a messaging and streaming broker

Risk score
52/100
CVSS
7.1 v3.1
Exploit chance (30 days)
0.3%
Published
25 Sep 2026

Open in the live forecast Today's forecast

What to know

What it is
RabbitMQ is a messaging and streaming broker. From 3.13.0 until 3.13.18, 4.0.23, 4.1.14, 4.2.9, and 4.3.3, native MQTT and MQTT over WebSocket behind a trusted PROXY Protocol frontend could lose the proxy-derived client address before the MQTT authentication path checked loopback_users, causing the frontend-to-broker …
Affected
Broadcom Rabbitmq Server before 3.13.18, 4.0.23, 4.1.14, 4.2.9, 4.3.3
Fix
Upgrade Broadcom Rabbitmq Server to 3.13.18, 4.0.23, 4.1.14, 4.2.9 or 4.3.3 (whichever matches your release line), or later.
Exploitation
Public proof of concept

Story map

Story map: Broadcom Rabbitmq ServerTHE FLAWSTHE FIXCVE-2026-67411RabbitMQ is a messaging andstreaming brokerCVSS 7.1 · EPSS 0%CVE-2026-67237RabbitMQ is a messaging andstreaming brokerCVSS 9.3 · EPSS 0%CVE-2026-66070RabbitMQ is a messaging andstreaming brokerCVSS 8.8 · EPSS 0%CVE-2026-67231RabbitMQ is a messaging andstreaming brokerCVSS 9.1 · EPSS 0%Upgrade Broadcom Rabbitmq…3.13.18 · 4.0.23 · 4.1.14 · 4.2.9 ·4.3.3 · 4.2.8or later on your release lineWho is exposedBroadcom Rabbitmq Serverbefore 4.2.8, 4.3.2AMBER · PATCH THIS WEEKBroadcomRabbitmq ServerRabbitMQ is a messaging andstreaming broker. From 4.2.0until 4.2.8 and 4.3.2,set_token_auth/2 inserted abearer token from theAuthorization header oraccess_token cookie into OAuth…Where it standsPublic proof of conceptCONNECTS TOSame weaknessIncorrect authorisation (CWE-863)336 other warnings in 30 days →Same productEarlier Broadcom Rabbitmq Server warnings45 in the last 90 days →
Story map: the flaws, the fix, how it unfolded and what it connects to. Boxes link to the record or article.

At a glance

Broadcom Rabbitmq Server: Amber, patch this week. RabbitMQ is a messaging and streaming broker. From 4.2.0 until 4.2.8 and 4.3.2, set_token_auth/2 inserted a bearer token from the Authorization header or access_token cookie into OAuth bootstrap JavaScript without escaping, allowing attacker-controlled token content to execute JavaScript in the management UI origin. T…

The flaws

  • CVE-2026-67411: RabbitMQ is a messaging and streaming broker (CVSS 7.1 · EPSS 0%)
  • CVE-2026-67237: RabbitMQ is a messaging and streaming broker (CVSS 9.3 · EPSS 0%)
  • CVE-2026-66070: RabbitMQ is a messaging and streaming broker (CVSS 8.8 · EPSS 0%)
  • CVE-2026-67231: RabbitMQ is a messaging and streaming broker (CVSS 9.1 · EPSS 0%)

The fix

Upgrade Broadcom Rabbitmq Server: 3.13.18 · 4.0.23 · 4.1.14 · 4.2.9 · 4.3.3 · 4.2.8 or later on your release line

Who is exposed: Broadcom Rabbitmq Server before 4.2.8, 4.3.2

Where it stands

  • Public proof of concept

Connects to

Why it is Yellow

  • CVSS 7.1 high
  • Public exploit or proof of concept referenced

References

Original description

RabbitMQ is a messaging and streaming broker. From 3.13.0 until 3.13.18, 4.0.23, 4.1.14, 4.2.9, and 4.3.3, native MQTT and MQTT over WebSocket behind a trusted PROXY Protocol frontend could lose the proxy-derived client address before the MQTT authentication path checked loopback_users, causing the frontend-to-broker address to be treated as loopback. An attacker who can reach the trusted frontend and has valid credentials for a loopback-restricted account can therefore bypass the source-address restriction; the issue does not bypass password authentication. This issue is fixed in versions 3.13.18, 4.0.23, 4.1.14, 4.2.9, and 4.3.3.

Last activity 25 Sep 2026. Patch Forecast updates every hour.