Read the docs
TI-2026-47551 Aliases CVE-2026-67235

RabbitMQ: AMQP 0-9-1 body assembly never validates accumulated size

Priority LOW 31CWE-770Published · 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 · High
Fix status
Partial Red Hat: 1 fixed, 2 without a fix

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

Summary

RabbitMQ is a messaging and streaming broker. Prior to versions 4.3.0, 4.2.6, 4.1.11, 4.0.20, and 3.13.15, The content-header BodySize (a uint64) was stored without validation against max_message_size. The size check ran only when assembly completed. By declaring body_size = 2^63-1 and then streaming fragments, a client ensured that check_msg_size never fired, so the accumulated body size went unbounded. A reader process accumulates memory until the memory alarm fires, degrading all publishers cluster-wide, or until the node runs out of memory. The memory alarm provides only partial mitigation, since it is reactive rather than preventive. AMQP 0-9-1 is the most widely used protocol, and any publisher can trigger this condition. Preconditions include Any authenticated AMQP 0-9-1 client with publish permission can exploit this.. This issue is fixed in versions 4.3.0, 4.2.6, 4.1.11, 4.0.20, and 3.13.15.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00302 23rd percentileScored 2026-11-07
Fix Partial rabbitmq-server (rabbitmq): 4.2.6, 4.1.11, 4.0.20 +1Red Hat: 1 advisoryRed Hat: 1 fixed, 2 without a fix

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
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.2.0 to before 4.2.6; 4.1.0 to before 4.1.11; 4.0.0 to before 4.0.20; 3.13.0 to before 3.13.154.2.6, 4.1.11, 4.0.20, 3.13.15Patch availableCNA
  • rabbitmq-server Vendorrabbitmq Affected 4.2.0 to before 4.2.6; 4.1.0 to before 4.1.11; 4.0.0 to before 4.0.20; 3.13.0 to before 3.13.15 Fixed in 4.2.6, 4.1.11, 4.0.20, 3.13.15 Patch available CNA

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:broadcom:rabbitmq_server:*:*:*:*:*:*:*:*3.13.0 to before 3.13.15; 4.0.0 to before 4.0.20; 4.1.0 to before 4.1.11; 4.2.0 to before 4.2.6VulnerableBroadcom
  • cpe:2.3:a:broadcom:rabbitmq_server:*:*:*:*:*:*:*:* Versions 3.13.0 to before 3.13.15; 4.0.0 to before 4.0.20; 4.1.0 to before 4.1.11; 4.2.0 to before 4.2.6 Vulnerable ·Broadcom

Remediation

  • Fix · CNA rabbitmq-server (rabbitmq) Fixed in 4.2.6, 4.1.11, 4.0.20, 3.13.15

Red Hat 1 advisory

  • RHSA-2026:67552 Released 2026-09-15 · Red Hat rating Important
    Red Hat Hardened Images RPMs bug fix and enhancement update
    • Red Hat Hardened Images rabbitmq-server4.3-4.3.6-1.hum1@aarch64, rabbitmq-server4.3-4.3.6-1.hum1@src, rabbitmq-server4.3-4.3.6-1.hum1@x86_64

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 18.0AffectedNo fix yet: Fix deferred
Red Hat Hardened ImagesFixed RHSA-2026:67552
Not affected: 3 products
  • Red Hat OpenStack Platform 13 (Queens)
  • Red Hat OpenStack Platform 16.2
  • Red Hat OpenStack Platform 17.1

Timeline

  1. 2026-10-02 Threatist record created from CVE-2026-67235
  2. 2026-10-20 CVSS score added · NVD

References

  • 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