Executive brief
RabbitMQ, a widely used message broker for handling data between applications, contains a flaw in its management interface. The system fails to properly limit the size of incoming data requests, allowing them to exceed safety thresholds. An attacker could exploit this to overwhelm the server's memory or processing resources, potentially leading to a service outage or degraded performance.
Technical details
A resource exhaustion vulnerability exists in the RabbitMQ Management Plugin due to improper validation of HTTP request body sizes. The 'read_complete_body' function in the HTTP API checks the accumulated payload size before processing the final data chunk but fails to verify the total combined size after the final chunk is appended. This allows valid JSON bodies that exceed the 'max_http_body_size' configuration to be accepted and processed. An authenticated attacker with access to the management API can send oversized payloads to the 'with_decode' or 'direct_request' paths, potentially leading to a Denial of Service (DoS) through memory exhaustion. The issue is resolved in versions 3.13.14, 4.0.19, 4.1.10, and 4.2.5.
Affected products
- RabbitMQ RabbitMQ Server >= 3.13.0, < 3.13.14; >= 4.0.0, < 4.0.19; >= 4.1.0, < 4.1.10; >= 4.2.0, < 4.2.5
Timeline
- 2026-03-12: patched: Fixes merged into main and v4.2.x branches
- 2026-03-17: other: Release of version 4.2.5
- 2026-06-18: advisory: GitHub Security Advisory GHSA-5cmq-vp28-xqrj published
- 2026-07-10: disclosed: CVE-2026-57212 published to NVD
References
- https://github.com/rabbitmq/rabbitmq-server/commit/3976d148901bdfa82e1cd60b7a4534e073266ba5
- https://github.com/rabbitmq/rabbitmq-server/commit/b8fc2ef7c50a2797d15e1ea7cf34f290032303bb
- https://github.com/rabbitmq/rabbitmq-server/pull/15712
- https://github.com/rabbitmq/rabbitmq-server/pull/15714
- https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.5
- https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-5cmq-vp28-xqrj