CVE-2026-57212: RabbitMQ resource exhaustion in management HTTP API via oversized JSON

CVE-2026-57212 · Severity: info · CVSS 7.1 · Published 2026-07-10

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.

Technologies: Broadcom Rabbitmq Server. Vendors: Broadcom.

Quick answers

Is CVE-2026-57212 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-57212 being exploited in the wild.
How severe is CVE-2026-57212?
Informational severity, with a CVSS score of 7.1, published 10 July 2026.
Which products and versions are affected?
Broadcom 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.
Is there a fix for CVE-2026-57212?
A patch was published on 2026-03-12: Fixes merged into main and v4.2.x branches Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-57212 attacked?
It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-57212?
Check whether you run Broadcom Rabbitmq Server at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

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

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.