RabbitMQ is a messaging and streaming broker. In the affected revision identified by the advisory, the AMQP 1.0 server_mode parser in deps/amqp10_common/src/amqp10_binary_parser.erl stops at the first body section and preserves the remaining bytes in bare_and_footer without validating message-section order. An authenticated publisher with write permission can place a properties section carrying a forged user-id after the body, causing rabbit_access_control:check_user_id/2 to see no user-id while permissive downstream AMQP 1.0 decoders or AMQP 0-9-1 conversion through classic and quorum queues expose the forged identity. Applications that rely on RabbitMQ-validated user-id metadata can therefore accept attacker-controlled publisher attribution. Strict consumers that reject out-of-order sections are not vulnerable to identity spoofing, and the issue does not bypass broker routing or destination authorization. This issue is fixed in version 4.3.5.
https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-6588-rqcr-59pw
https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.5
https://github.com/rabbitmq/rabbitmq-server/pull/17049
https://github.com/rabbitmq/rabbitmq-server/commit/c3dec83d4c0da4a589c1d179b4fff6f4965301d1
https://github.com/rabbitmq/rabbitmq-server/commit/918d8de2705b8a425c73f52cb2ddb14e6a1f4978
Published: 2026-11-20
Updated: 2026-11-20
Base Score: 3.5
Vector: CVSS2#AV:N/AC:M/Au:S/C:N/I:P/A:N
Severity: Low
Base Score: 6.5
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
Severity: Medium
Base Score: 5.3
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N
Severity: Medium