Rabbitmq server: RabbitMQ is a messaging and streaming broker. (CVE-2026-67233)

RabbitMQ server versions before 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.1 contain a flaw in the shovel management resource's authorization logic. The is_authorized/2 function delegates to rabbit_mgmt_util:is_authorized_monitor/2, which accepts the monitoring tag intended for read-only access. However, allowed_methods includes DELETE, and the delete_resource/2 function deletes or restarts shovel runtime parameters without additional role verification. Consequently, a monitoring user can perform state-changing operations like deleting or restarting any shovel in any vhost they can access. This is a deviation from the expected behavior where such operations should be restricted to users with policymaker roles. The vulnerability requires the rabbitmq_shovel and rabbitmq_shovel_management plugins to be enabled and valid monitoring credentials. The issue is resolved in versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.1.

An attacker with monitoring credentials can delete or restart any dynamic shovel in any virtual host they can access, performing state-changing operations that should be restricted. This could disrupt message streaming and broker operations by removing or restarting shovels without proper authorization. The impact is limited to users who already have monitoring privileges and the affected RabbitMQ plugins enabled.

This vulnerability is fixed in RabbitMQ versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.1. Users should upgrade to one of these versions or later to remediate the issue. No additional mitigation is required if the system is already updated. Ensure that the rabbitmq_shovel and rabbitmq_shovel_management plugins are used with updated versions to prevent unauthorized shovel deletions or restarts.