Description
RabbitMQ is a messaging and streaming broker. Prior to 4.2.6, the RabbitMQ stream listener does not enforce the configured stream frame-size limit while assembling frames during authentication and before Tune negotiation, allowing an unauthenticated remote client to declare oversized frame lengths and consume broker memory in rabbit_stream_core. This issue is fixed in version 4.2.6.
Affected products
broadcom: rabbitmq server
References7
- github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-f3… ExploitVendor Advisory
- github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-f3… ExploitVendor Advisory
- github.com/rabbitmq/rabbitmq-server/commit/595ec28fa1621b1f2c28… Patch
- github.com/rabbitmq/rabbitmq-server/commit/773a49c4921e8be99026… Patch
- github.com/rabbitmq/rabbitmq-server/pull/16171 Issue TrackingPatch
- github.com/rabbitmq/rabbitmq-server/pull/16173 Issue TrackingPatch
- github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.6 Release Notes
Metrics
- CVSS 3.1
-
7.5
HIGH
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - EPSS — exploit probability
- 1% percentile: 46 · as of 15 November 2026
- CWE
- CWE-770
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.