CVE-2026-121714

RabbitMQ: AMQP 1.0 post-body properties bypass user-ID validation and reach consumers

State
Published
Severity
5.3 Medium
Published
Nov 20, 2026
Updated
Nov 20, 2026
Reserved
Nov 3, 2026

Read the record on cve.org

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.

Scores

CVSSScoreVectorSource
4.05.3 MediumCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:NGitHub_M

Weaknesses

  • CWE-20 Improper Input Validation
  • CWE-345 Insufficient Verification of Data Authenticity
  • CWE-436 Interpretation Conflict

Affected Products

ProductVersions
rabbitmq-serverrabbitmq
  • >= 4.3.0, < 4.3.5Affected

References

Every record here comes from the CVE Program's CVE List. © 1999-2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.

© 2026 NVIDIA, the NVIDIA logo, and NVIDIA Inception are trademarks and/or registered trademarks of NVIDIA Corporation in the U.S. and other countries.