Servers and applications
CVE-2026-57212
RabbitMQ management HTTP API accepts request bodies larger than configured max_http_body_size
- Severity
- High 7.1
- Published
- 18 Jun 2026
- Last changed
- 25 Oct 2026
- Added to UpHeron
- 1 Nov 2026
- Fixed in
- 3.13.14, 4.0.19, 4.1.10, 4.2.5
- Exploit chance
- 0.4% in the next 30 daysHigher than 38% of CVEs. EPSS by FIRST, 19 Nov 2026
- Attack
- Over the network · Needs a user account · No user action needed
- Attacker can
- Take it down
- CVSS vector
CVSS:4.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- Also known as
- GHSA-5cmq-vp28-xqrj
- Sources
- NVD, Project advisories (GitHub)
Description
The rabbitmq_management HTTP API appears to enforce a request body size limit through max_http_body_size, but in practice it accepts oversized valid JSON bodies and processes them normally.
The root cause is that the helper responsible for reading the request body checks the accumulated size only before reading the final chunk and does not validate the final combined size after appending that chunk.
- Vulnerability type: Request body size limit bypass
- Affected component: rabbitmq_management
- Verification date: 2026-03-11
Even when an operator configures a management HTTP API body size limit, endpoints that use the with_decode or direct_request paths do not enforce that limit completely.
As a result, an attacker can send JSON requests larger than the configured limit, and management operations that should have been blocked are still processed.
The exact impact depends on the endpoint, but at minimum the following problems exist:
Affected software
| Software | Affected versions |
|---|---|
RabbitMQServers and applications · cpe:a:broadcom:rabbitmq_server |
|
RabbitMQServers and applications · github:rabbitmq/rabbitmq-server |
|
About RabbitMQ
open source message broker, sometimes referred to as "Rabbit"
- Docker Hub pulls
- 3,918,841,187Docker Hub, 15 Nov 2026
- GitHub stars
- 13,973GitHub, 15 Nov 2026
- Forks
- 4,032GitHub, 15 Nov 2026
- Latest release
- v4.4.0GitHub, 15 Nov 2026
- Released
- 19 Oct 2026GitHub
- Developer
- Jean-Sébastien PédronWikidata
- License
- Mozilla Public License, version 2.0Wikidata
- Written in
- ErlangWikidata
- First published on GitHub
- 20 Sept 2010GitHub
Website Source code Docker image
Release lines
| Release | Latest | Security fixes |
|---|---|---|
| 4.4 | 4.4.0 | Until 31 Jul 2027 |
| 4.3 | 4.3.7 | Until 31 Jan 2027 |
| 4.2 | 4.2.9 | Ended 31 Jul 2026 |
| 4.1 | 4.1.8 | Ended 30 Jan 2026 |
| 4.0 | 4.0.9 | Ended 30 Apr 2025 |
| 3.13 | 3.13.7 | Ended 30 Sept 2024 |
From endoflife.date.
Vulnerabilities in RabbitMQ
- In our list
- 107
- Published in the last 12 months
- 89
- Critical, last 12 months
- 4
- High, last 12 months
- 22
- Known exploited
- 0
- GHSA-3wxh-g236-vm46LDAP authentication failures allow unauthenticated log amplificationHigh 8.2 25 Oct 2026
- GHSA-g73v-gcjq-2g4hAMQP message conversion can repeatedly disconnect AMQP 0-9-1 consumersMedium 6.3 25 Oct 2026
- GHSA-6wvj-vwrc-wcrmHTML injection in management UI OAuth login warningMedium 5.7 25 Oct 2026
- GHSA-mhh3-4wv2-rrj7SASL credentials are not redacted from `amqp10_client` crash dumps and `sys:get_status` outputMedium 5.7 25 Oct 2026
- GHSA-9h6g-46wc-m2f5Memory DoS via incomplete AMQP 0-9-1 messagesHigh 7.1 25 Oct 2026
- GHSA-j6hc-926v-qwq2RabbitMQ STOMP consumers retain OAuth queue access after JWT expirationMedium 4.9 18 Sept 2026
References
- NVD https://nvd.nist.gov/vuln/detail/CVE-2026-57212
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-57212
- GitHub Advisory Database https://github.com/advisories/GHSA-5cmq-vp28-xqrj
- github.com https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-5cmq-vp28-xqrj