CVE-2026-57212 Details
Description
RabbitMQ is a messaging and streaming broker. Prior to 3.13.14, 4.0.19, 4.1.10, and 4.2.5, the rabbitmq_management HTTP API accepts oversized valid JSON bodies on with_decode and direct_request paths because read_complete_body checks the accumulated size before the final chunk but not the final combined size. This issue is fixed in versions 3.13.14, 4.0.19, 4.1.10, and 4.2.5.
A vulnerability exists in the RabbitMQ Management HTTP API in versions prior to 3.13.14, 4.0.19, 4.1.10, and 4.2.5. The issue arises because the API improperly handles request body size limits, allowing oversized valid JSON bodies to be processed on endpoints that use the 'with_decode' and 'direct_request' paths. This occurs because the body size check only considers the accumulated size before the final chunk is read, failing to validate the total size after appending that chunk. As a result, management operations that should have been blocked are still executed, potentially leading to resource exhaustion and bypassing of body size restrictions on certain API endpoints.
Users should upgrade to RabbitMQ versions 3.13.14, 4.0.19, 4.1.10, or 4.2.5, where this vulnerability has been fixed.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Jul 13, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-770 | Allocation of Resources Without Limits or Throttling | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| broadcom rabbitmq server | >= 3.13.0, < 4.2.5 |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jul 13, 2026 | Initial Analysis | [email protected] |
| Jul 13, 2026 | CVE Modified | CISA-ADP |
| Jul 10, 2026 | New CVE Received | [email protected] |