Read the docs
TI-2026-74165 Aliases CVE-2026-67416

RabbitMQ symbolic body descriptor prefix collisions bypass AMQP validation

Priority MEDIUM 57CWE-20Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Attack requirements
None
Impact type
Denial of service
Confidentiality · integrity · availability
None · None · Low
Fix status
Partial Red Hat: 1 fixed, 5 without a fix

Attack profile from CVSS 4.0 · CNA. Fix status from CNA and Red Hat. Impact type from CWE-248.

Summary

RabbitMQ rabbitmq-server from 4.0.0 before 4.0.24, from 4.1.0 before 4.1.15, from 4.2.0 before 4.2.10, and from 4.3.0 before 4.3.4 is affected. The AMQP 1.0 parser matches textual prefixes of symbolic body descriptors without checking encoded symbol lengths (CWE-20). An authenticated publisher with write permission can store an unknown descriptor as a standard body section. Strict AMQP 1.0 consumers can terminate while decoding stored entries.

Written with Claude Haiku 5.5 from the sources below · 2026-10-28

Description from the CNA

RabbitMQ is a messaging and streaming broker. From 4.0.0 until 4.0.24, 4.1.15, 4.2.10, and 4.3.4, the optimized AMQP 1.0 server_mode parser in deps/amqp10_common/src/amqp10_binary_parser.erl matches the textual prefixes of symbolic data, sequence, and value body descriptors without verifying their encoded symbol lengths. An authenticated AMQP 1.0 publisher with write permission can submit a well-formed unknown descriptor that begins with a registered body descriptor, and RabbitMQ misclassifies and stores the bytes as a standard body section. Strict AMQP 1.0 consumers can terminate while decoding the stored entry. For bodies misclassified as data, AMQP 0-9-1 or other cross-protocol conversion performs full body decoding and can terminate the consumer protocol process, with acknowledgement-required delivery permitting repeated failures. Sequence and value classifications are normally transported as opaque encoded payloads on that conversion path. The broker remains alive, and the issue does not bypass routing or authorization. This issue is fixed in versions 4.0.24, 4.1.15, 4.2.10, and 4.3.4.

Why it matters now

Exploitation Proof of concept CISA SSVC · not in CISA KEV
EPSS 0.00621 50th percentileScored 2026-11-08
Fix Partial rabbitmq-server (rabbitmq): 4.0.24, 4.1.15, 4.2.10 +1Red Hat: 1 advisoryRed Hat: 1 fixed, 5 without a fix

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
Poc
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
rabbitmqrabbitmq-server4.0.0 to before 4.0.24; 4.1.0 to before 4.1.15; 4.2.0 to before 4.2.10; 4.3.0 to before 4.3.44.0.24, 4.1.15, 4.2.10, 4.3.4Patch availableCNA
  • rabbitmq-server Vendorrabbitmq Affected 4.0.0 to before 4.0.24; 4.1.0 to before 4.1.15; 4.2.0 to before 4.2.10; 4.3.0 to before 4.3.4 Fixed in 4.0.24, 4.1.15, 4.2.10, 4.3.4 Patch available CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:broadcom:rabbitmq_server:*:*:*:*:*:*:*:*——Broadcom
  • cpe:2.3:a:broadcom:rabbitmq_server:*:*:*:*:*:*:*:* Versions — — ·Broadcom

Remediation

Upgrade rabbitmq-server to 4.0.24, 4.1.15, 4.2.10, or 4.3.4 for the matching release line. Red Hat fixes Red Hat Hardened Images in RHSA-2026:82703. Red Hat has no fix planned for Red Hat OpenStack Platform 13 (Queens), 16.2, and 17.1. The sources list no fixed version for Red Hat OpenStack Platform 18.0.

Written with Claude Haiku 5.5 from the sources below · 2026-10-28

  • Fix · CNA rabbitmq-server (rabbitmq) Fixed in 4.0.24, 4.1.15, 4.2.10, 4.3.4

Red Hat 1 advisory

  • RHSA-2026:82703 Released 2026-10-14 · Red Hat rating Moderate
    Red Hat Hardened Images RPMs bug fix and enhancement update
    • Red Hat Hardened Images rabbitmq-server4.3-4.3.6-1.1.hum1@aarch64, rabbitmq-server4.3-4.3.6-1.1.hum1@s390x, rabbitmq-server4.3-4.3.6-1.1.hum1@src +1

Vendor assessments

Red Hat

Red Hat rating: Moderate. Red Hat's page for this CVE →

ProductStatusPlan or fix
Red Hat Hardened ImagesAffectedNo fix planned: Will not fix
Red Hat OpenStack Platform 13 (Queens)AffectedNo fix planned: Out of support scope
Red Hat OpenStack Platform 16.2AffectedNo fix planned: Out of support scope
Red Hat OpenStack Platform 17.1AffectedNo fix planned: Out of support scope
Red Hat OpenStack Platform 18.0AffectedNo fix yet: Fix deferred
Red Hat Hardened ImagesFixed RHSA-2026:82703

Timeline

  1. 2026-10-14 Threatist record created from CVE-2026-67416
  2. 2026-10-16 CISA SSVC decision points changed
  3. 2026-10-16 Priority changed: LOW → MEDIUM
  4. 2026-10-18 Fix available: RHSA-2026:82703 · Red Hat
  5. 2026-10-18 Fix available: Red Hat Hardened Images · Red Hat
  6. 2026-10-18 CVSS score added · Red Hat
  7. 2026-11-07 EPSS moved to the 50th–90th percentile

References

Other 6

  • TI-2026-41154 Improper authentication in rabbitmq-server CVSS 3.1CRITICAL 10.0
  • TI-2026-41149 RabbitMQ: UNC SSRF affecting the management UI on Windows CVSS 3.1CRITICAL 10.0
  • TI-2026-41158 Resource allocation without limits in rabbitmq-server CVSS 3.1HIGH 7.5
  • TI-2026-47695 RabbitMQ: OAuth2 Client Secret Exposed via Unauthenticated JavaScript Endpoint CVSS 4.0HIGH 8.2
  • TI-2026-47694 RabbitMQ: JWKS Fetch Ignores HTTP Response Status Code - Signing Key Destruction Causes Authentication DoS CVSS 4.0HIGH 8.2
  • TI-2026-45167 RabbitMQ Java client: Unvalidated Class.forName in JSON-RPC ProcedureDescription enables arbitrary class loading CVSS 4.0HIGH 7.5
See all 100 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences