High · published September 24, 2026
RabbitMQ is a messaging and streaming broker. Prior to versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.1, The shovel management resource's is_authorized/2 delegates to rabbit_mgmt_util:is_authorized_monitor/2, which accepts the monitoring tag. But allowed_methods includes DELETE, and delete_resource/2 deletes / restarts shovel runtime parameters with no additional role check. A monitoring user , intended to have read-only visibility , can therefore delete or restart any shovel in any vhost they can see. A read-only monitoring user can delete or restart any dynamic shovel , a state-changing operation that the equivalent /api/parameters endpoint correctly restricts to policymaker. Preconditions include rabbitmq_shovel + rabbitmq_shovel_management plugins enabled Attacker has credentials with the monitoring tag. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.1.
| Product | Versions | Fixed in |
|---|---|---|
| broadcom/rabbitmq_server | ≥ 3.13.0, < 3.13.15 | 3.13.15 |
| broadcom/rabbitmq_server | ≥ 4.0.0, < 4.0.20 | 4.0.20 |
| broadcom/rabbitmq_server | ≥ 4.1.0, < 4.1.11 | 4.1.11 |
| broadcom/rabbitmq_server | ≥ 4.2.0, < 4.2.6 | 4.2.6 |
| broadcom/rabbitmq_server | ≥ 4.3.0, < 4.3.1 | 4.3.1 |