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.
CVE-2026-57212
This high-severity CVE scores 7.7 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 67% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.7
- EG Score
- 7.7(medium)
- EG Risk
- 51(Track)EG Risk 51/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity77% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 35.4%
- KEV
- Not listed
Published
July 10, 2026
Last Modified
July 13, 2026
Advisory Details (6)
Auto-updated Jul 10, 2026RabbitMQ management HTTP API accepts request bodies larger than configured max_http_body_size · Advisory · rabbitmq/rabbitmq-server · GitHub
https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-5cmq-vp28-xqrjRabbitMQ 4.2.5
Patch available: rabbitmq/rabbitmq-server v4.2.5
https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.5HTTP API: refactor `read_complete_body/1` (backport #15712)
Fix merged in rabbitmq/rabbitmq-server PR #15714 on 2026-03-12 — awaiting tagged release
https://github.com/rabbitmq/rabbitmq-server/pull/15714HTTP API: refactor `read_complete_body/1`
Fix merged in rabbitmq/rabbitmq-server PR #15712 on 2026-03-12 — awaiting tagged release
https://github.com/rabbitmq/rabbitmq-server/pull/15712commit b8fc2ef7c50a (rabbitmq/rabbitmq-server)
Fix landed in rabbitmq/rabbitmq-server commit b8fc2ef7c50a — awaiting tagged release
https://github.com/rabbitmq/rabbitmq-server/commit/b8fc2ef7c50a2797d15e1ea7cf34f290032303bbcommit 3976d148901b (rabbitmq/rabbitmq-server)
Fix landed in rabbitmq/rabbitmq-server commit 3976d148901b — awaiting tagged release
https://github.com/rabbitmq/rabbitmq-server/commit/3976d148901bdfa82e1cd60b7a4534e073266ba5Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 24× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:20 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-14 10:41 UTCEG score recompute▲ 0.60
- 2026-07-14 00:27 UTCNVD updateCVSS v3 → 7.7
- 2026-07-13 22:31 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-10 20:39 UTCEG score recompute
- 2026-07-10 20:37 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-770
- CVE-2018-20033EG 9.8CRITICAL
- CVE-2019-11479NVD 7.5EG 9.0EPSS 100%HIGH
- CVE-2019-11478NVD 5.3EG 9.0EPSS 100%MEDIUM
- CVE-2019-10088EG 8.8EPSS 91%HIGH
- CVE-2018-15462EG 8.6HIGH
- CVE-2018-15460EG 8.6HIGH
- CVE-2018-0137EG 8.6HIGH
- CVE-2008-5180NVD 5.3EG 7.9EPSS 99%MEDIUM
- CVE-2019-10094EG 7.8HIGH
- CVE-2018-16865EG 7.8HIGH
Frequently asked(5)
What is CVE-2026-57212?
When was CVE-2026-57212 disclosed?
Is CVE-2026-57212 actively exploited?
What is the CVSS score of CVE-2026-57212?
How do I remediate CVE-2026-57212?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-57212
Is Your Infrastructure Affected by CVE-2026-57212?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.