Patch Forecast
Yellow warning
Plan into this sprint.

CVE-2026-67241

RabbitMQ is a messaging and streaming broker

Risk score
44/100
CVSS
6.5 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 4.2.0 until 4.2.9 and 4.3.3, AMQP 1.0 management exchange.declare skips alternate-exchange permission check. pUT /exchanges/:name (lines 192-240) checks only configure on the declared exchange and passes XArgs straight to rabbitexchange:declare/7. It omits the checkre…
Affected
Broadcom Rabbitmq Server before 4.2.9, 4.3.3
Fix
Upgrade Broadcom Rabbitmq Server to 4.2.9 or 4.3.3 (whichever matches your release line), or later.
Exploitation
No known exploitation

Story map

Story map: Broadcom Rabbitmq ServerTHE FLAWSTHE FIXCVE-2026-67241RabbitMQ is a messaging andstreaming brokerCVSS 6.5 · 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…4.2.9 · 4.3.3 · 4.2.8 · 4.3.2 ·3.13.17 · 4.0.22or 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 standsNo known exploitationCONNECTS TOSame weaknessMissing authorisation (CWE-862)399 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-67241: RabbitMQ is a messaging and streaming broker (CVSS 6.5 · 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: 4.2.9 · 4.3.3 · 4.2.8 · 4.3.2 · 3.13.17 · 4.0.22 or later on your release line

Who is exposed: Broadcom Rabbitmq Server before 4.2.8, 4.3.2

Where it stands

  • No known exploitation

Connects to

Why it is Yellow

  • CVSS 6.5 medium

References

Original description

RabbitMQ is a messaging and streaming broker. From 4.2.0 until 4.2.9 and 4.3.3, AMQP 1.0 management exchange.declare skips alternate-exchange permission check. pUT /exchanges/:name (lines 192-240) checks only configure on the declared exchange and passes XArgs straight to rabbitexchange:declare/7. It omits the checkreadpermitted(X) + checkwritepermitted(AE) that rabbitchannel.erl:2540-2548 enforces for the alternate-exchange argument on the AMQP 0-9-1 path. The same file already implements the analogous DLX check for queues (lines 708-719), confirming this is a missing-check bug rather than intentional A user with only configure on exchange X can route X's unroutable messages into an alternate exchange they have no write permission AMQP 1.0 enabled (default in RabbitMQ 4.x) Attacker has configure on at least one exchange but lacks write on the target. This issue is fixed in versions 4.2.9 and 4.3.3.

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