RabbitMQ Management displays an AMQP authorization‑error reason that contains an attacker‑controlled queue name rendered as raw HTML when the OAuth management UI is enabled. The injected queue name can include a base element that rewrites the automatic relative refresh, bypassing the Content Security Policy that omits base‑uri and connect‑src directives. An attacker hosting an endpoint that accepts Cross‑Origin Resource Sharing requests from the management origin can receive the victim’s Authorization header. Consequently, an attacker can obtain privileged credentials and use them to gain unauthorized access to the RabbitMQ system, a weakness identified as CWE‑862.

Versions from 3.13.0 through 3.13.18, and the specific vulnerable releases 3.13.0‑3.13.19, 4.0.24, 4.1.15, 4.2.10, and 4.3.5 are affected. Updating to version 3.13.19, 4.0.24, 4.1.15, 4.2.10, 4.3.5 or any newer release resolves the issue.

The CVSS score of 4.5 indicates moderate severity, and no EPSS score is available. The vulnerability is not listed in the CISA KEV catalog. Exploitation requires an attacker with queue configure permission, an administrator who can view but not read the queue, and the administrator clicking the Get Message(s) button. The attack is therefore possible in environments with highly privileged roles and a specific interaction pattern, making the likelihood of real‑world exploitation limited but not negligible.