CVE-2026-57212

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 79% 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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
7.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.1
EG Score
7.1(medium)
EPSS
21.1%
KEV
Not listed

Published

July 10, 2026

Last Modified

July 10, 2026

Advisory Details (6)

Auto-updated Jul 10, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available

RabbitMQ 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-xqrj
github_release Patch Available

RabbitMQ 4.2.5

Patch available: rabbitmq/rabbitmq-server v4.2.5

https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.5
github_pr

HTTP 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/15714
github_pr

HTTP 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/15712
github_commit

commit b8fc2ef7c50a (rabbitmq/rabbitmq-server)

Fix landed in rabbitmq/rabbitmq-server commit b8fc2ef7c50a — awaiting tagged release

https://github.com/rabbitmq/rabbitmq-server/commit/b8fc2ef7c50a2797d15e1ea7cf34f290032303bb
github_commit

commit 3976d148901b (rabbitmq/rabbitmq-server)

Fix landed in rabbitmq/rabbitmq-server commit 3976d148901b — awaiting tagged release

https://github.com/rabbitmq/rabbitmq-server/commit/3976d148901bdfa82e1cd60b7a4534e073266ba5

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 10× 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.

  1. 2026-07-13 10:06 UTCEG score recompute
  2. 2026-07-13 06:13 UTCEPSS rescore
  3. 2026-07-13 06:13 UTCEPSS rescore
  4. 2026-07-12 21:49 UTCEG score recompute
  5. 2026-07-12 09:32 UTCEG score recompute
  6. 2026-07-12 05:46 UTCEPSS rescore
  7. 2026-07-11 21:15 UTCEG score recompute
  8. 2026-07-11 08:58 UTCEG score recompute
  9. 2026-07-10 20:39 UTCEG score recompute
  10. 2026-07-10 20:37 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-57212?
CVE-2026-57212 is a high vulnerability published on July 10, 2026. RabbitMQ is a messaging and streaming broker. Prior to 3.13.14, 4.0.19, 4.1.10, and 4.2.5, the rabbitmqmanagement HTTP API accepts oversized valid JSON bodies on withdecode and directrequest paths because readcomplete_body checks the accumulated size before the final chunk but not the final…
When was CVE-2026-57212 disclosed?
CVE-2026-57212 was first published in the National Vulnerability Database on July 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-57212 actively exploited?
CVE-2026-57212 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 21.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-57212?
CVE-2026-57212 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-57212?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-57212, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-57212

Explore →

Is Your Infrastructure Affected by CVE-2026-57212?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs