PoC Monitor
← All CVEs
CVE-2026-67235published 23 Sep 2026 20:36 UTCData: JSON · API

RabbitMQ rabbitmq-server

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

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.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.1high · scored by CNA · CWE-770
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

rabbitmq rabbitmq-server
  • >= 4.2.0, < 4.2.6
  • >= 4.1.0, < 4.1.11
  • >= 4.0.0, < 4.0.20
  • >= 3.13.0, < 3.13.15

Fixed in 4.2.6, 4.1.11, 4.0.20, 3.13.15

Mitigation

Upgrade rabbitmq-server to 4.2.6 or 4.1.11 or 4.0.20 or 3.13.15 or later.

References

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published23 Sep 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.