CVE-2026-121714

Status: Received

Description

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.

Published
November 20, 2026 8:17 PM
Last Modified
November 20, 2026 8:17 PM
Source
[email protected]

Weaknesses (CWE)

CWE-20 CWE-345 CWE-436

References

Contact Us

Get the CyboWatch SIEM platform, hosting, and 24×7 SOC analysts. Send an enquiry, or call or email us to get started.

Send an enquiry