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.
References
| Link | Resource |
|---|---|
| https://github.com/rabbitmq/rabbitmq-server/commit/595ec28fa1621b1f2c28124e4e0466a8ad963547 | Patch |
| https://github.com/rabbitmq/rabbitmq-server/commit/773a49c4921e8be990262a2d609c35916825679e | Patch |
| https://github.com/rabbitmq/rabbitmq-server/pull/16171 | Issue Tracking Patch |
| https://github.com/rabbitmq/rabbitmq-server/pull/16173 | Issue Tracking Patch |
| https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.6 | Release Notes |
| https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-f364-87q5-j35q | Exploit Vendor Advisory |
| https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-f364-87q5-j35q | Exploit Vendor Advisory |
Configurations
History
No history.
Information
Published : 2026-07-10 21:16
Updated : 2026-07-13 20:49
NVD link : CVE-2026-57220
Mitre link : CVE-2026-57220
CVE.ORG link : CVE-2026-57220
JSON object : View
Products Affected
broadcom
- rabbitmq_server
CWE
CWE-770
Allocation of Resources Without Limits or Throttling
