CVE-2026-121714: RabbitMQ: AMQP 1.0 post-body properties bypass user-ID validation and reach consumers
RabbitMQ is a messaging and streaming broker. In the affected revision identified by the advisory, the AMQP 1.0 servermode parser in deps/amqp10common/src/amqp10binaryparser.erl stops at the first body section and preserves the remaining bytes in bareandfooter 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 rabbitaccesscontrol:checkuserid/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.
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
RabbitMQto a version that resolves this vulnerability.Fixed in 4.3.5