Resource exhaustion in Broadcom Rabbitmq Server

CVE-2026-67235

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.

Published · last modified .

CVSS v3 metric

CVSS v3 base score 6.5 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.

EPSS exploit prediction

EPSS: 0.003 (23.0th percentile), scored .

Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 23rd percentile — 23.0% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.

EPSS trend (30 days)EPSS over the last 30 days for CVE-2026-67235: held from 0.003 to 0.003.

EPSS over last 30 days · oldest: 0.003 · newest: 0.003 · change: +0.000

Affected products

Weakness classification (CWE)

References

Frequently asked questions

What is CVE-2026-67235?
CVE-2026-67235 is a medium-severity vulnerability in Broadcom Rabbitmq Server, classified under Allocation of Resources Without Limits or Throttling. CVSS score: 6.5/10. Published 2026-09-23.
How severe is CVE-2026-67235?
Medium severity. CVSS v3 base score is 6.5 out of 10.