CVE-2026-66070

High

Description

RabbitMQ is a messaging and streaming broker. Prior to versions 3.13.17, 4.0.22, 4.1.13, and 4.2.6, match_origin/1 returned the bare reflected Origin and allowed credentials even when the wildcard "" was configured, so the response echoed the attacker's origin together with Access-Control-Allow-Credentials. The affected code is rabbit_mgmt_cors.erl. When the management plugin is configured with a wildcard CORS origin (cors_allow_origins = ""), the handler reflects the request Origin back in Access-Control-Allow-Origin and also sends Access-Control-Allow-Credentials: true. A malicious web page that a signed-in administrator visits can then use that administrator's cached HTTP Basic credentials to issue authenticated, state-changing requests to the management API. Preconditions include The management plugin is configured with the wildcard cors_allow_origins = "*", which is an explicit operator misconfiguration A target administrator has a cached HTTP Basic-auth session in the browser. This issue is fixed in versions 3.13.17, 4.0.22, 4.1.13, and 4.2.6.

SeverityHigh
CVSS8.8
Exploit probability—
ProductBroadcom Rabbitmq Server
PublishedSep 23, 2026
First seenSep 23, 2026
Weakness typeCWE-942CWE-942

How to fix

Update
  • broadcom rabbitmq_server3.13.17, 4.0.22, 4.1.13, 4.2.6 or later

Affected products

ProductAffected versionsFixed in
broadcom rabbitmq_server3.13.0 ≤ v < 3.13.17, 4.0.0 ≤ v < 4.0.22, 4.1.0 ≤ v < 4.1.13, 4.2.0 ≤ v < 4.2.63.13.17, 4.0.22, 4.1.13, 4.2.6

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.