7.1
HIGH CVSS 4.0
CVE-2026-57212
RabbitMQ management HTTP API accepts request bodies larger than configured max_http_body_size
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.

INFO

Published Date :

July 10, 2026, 9:16 p.m.

Last Modified :

July 10, 2026, 9:16 p.m.

Remotely Exploit :

Yes !
Affected Products

The following products are affected by CVE-2026-57212 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

No affected product recoded yet

CVSS Scores
The Common Vulnerability Scoring System is a standardized framework for assessing the severity of vulnerabilities in software and systems. We collect and displays CVSS scores from various sources for each CVE.
Score Version Severity Vector Exploitability Score Impact Score Source
CVSS 4.0 HIGH [email protected]
Solution
Update RabbitMQ to a patched version to fix the JSON body handling vulnerability.
  • Update RabbitMQ to version 3.13.14 or later.
  • Update RabbitMQ to version 4.0.19 or later.
  • Update RabbitMQ to version 4.1.10 or later.
  • Update RabbitMQ to version 4.2.5 or later.
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-57212 is associated with the following CWEs:

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-57212 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-57212 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by [email protected]

    Jul. 10, 2026

    Action Type Old Value New Value
    Added Affected [{'vendor': 'rabbitmq', 'product': 'rabbitmq-server', 'versions': [{'status': 'affected', 'version': '>= 4.2.0, < 4.2.5'}, {'status': 'affected', 'version': '>= 4.1.0, < 4.1.10'}, {'status': 'affected', 'version': '>= 4.0.0, < 4.0.19'}, {'status': 'affected', 'version': '>= 3.13.0, < 3.13.14'}]}]
    Added 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.
    Added CVSS V4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
    Added CWE CWE-770
    Added Reference https://github.com/rabbitmq/rabbitmq-server/commit/3976d148901bdfa82e1cd60b7a4534e073266ba5
    Added Reference https://github.com/rabbitmq/rabbitmq-server/commit/b8fc2ef7c50a2797d15e1ea7cf34f290032303bb
    Added Reference https://github.com/rabbitmq/rabbitmq-server/pull/15712
    Added Reference https://github.com/rabbitmq/rabbitmq-server/pull/15714
    Added Reference https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.5
    Added Reference https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-5cmq-vp28-xqrj
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.