CVE-2026-121714

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

Published Nov 20, 2026 CVSS 4.0 · 5.3 Medium EPSS n/a KEV · Not listed
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.

Analysis

No analysis available yet

Remediation

No remediation available yet

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
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.
Title RabbitMQ: AMQP 1.0 post-body properties bypass user-ID validation and reach consumers
Weaknesses CWE-20
CWE-345
CWE-436
References
Metrics cvssV4_0

{'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'}

Subscriptions

No data.

Weaknesses
  • CWE-20

    Improper Input Validation

  • CWE-345

    Insufficient Verification of Data Authenticity

  • CWE-436

    Interpretation Conflict

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Nov 20, 2026, 7:46 PM
Reserved
Nov 3, 2026, 8:41 PM
Status
Received
Published
Nov 20, 2026, 8:17 PM
Modified
Nov 20, 2026, 8:17 PM