CVE-2026-57212

HIGHNVD 7.77.7—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.7 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 64% 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, nvd
Trending — 3 sources updated this weekElevated
7.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.7Exploit: Elevated riskExposed: 0

A fix is available — apply it.

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.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 computed
Severity77% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
36%
KEV
Not listed

Published

July 10, 2026

Last Modified

July 13, 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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrabbitmq-server4-2-main-4.2.8-1.hum12026-07-06redhat
redhatrabbitmq-server4-3-main-4.3.2-1.hum12026-07-06redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

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

All Vendor Advisories

(2)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 15× in last 7d / 35× 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-29 13:56 UTCVendor advisory
  2. 2026-07-29 01:39 UTCEG score recompute
  3. 2026-07-28 15:37 UTCEPSS rescore
  4. 2026-07-28 01:02 UTCEG score recompute
  5. 2026-07-27 14:14 UTCEPSS rescore
  6. 2026-07-27 00:27 UTCEG score recompute
  7. 2026-07-26 14:54 UTCEPSS rescore
  8. 2026-07-26 14:54 UTCEPSS rescore
  9. 2026-07-26 12:08 UTCEG score recompute
  10. 2026-07-25 14:18 UTCEPSS rescore
  11. 2026-07-25 14:18 UTCEPSS rescore
  12. 2026-07-24 14:18 UTCEPSS rescore
  13. 2026-07-24 14:18 UTCEPSS rescore
  14. 2026-07-23 14:18 UTCEPSS rescore
  15. 2026-07-23 03:20 UTCEG score recompute
  16. 2026-07-22 14:08 UTCEPSS rescore
  17. 2026-07-21 15:25 UTCEPSS rescore
  18. 2026-07-20 17:08 UTCEPSS rescore
  19. 2026-07-19 14:31 UTCEPSS rescore
  20. 2026-07-19 14:31 UTCEPSS rescore
  21. 2026-07-19 02:29 UTCEPSS rescore
  22. 2026-07-18 10:04 UTCEPSS rescore
  23. 2026-07-16 17:03 UTCEPSS rescore
  24. 2026-07-15 16:57 UTCEPSS rescore
  25. 2026-07-15 16:57 UTCEPSS rescore
Show 10 more
  1. 2026-07-15 02:00 UTCEPSS rescore
  2. 2026-07-15 02:00 UTCEPSS rescore
  3. 2026-07-14 10:41 UTCEG score recompute▲ 0.60
  4. 2026-07-14 00:27 UTCNVD updateCVSS v3 → 7.7
  5. 2026-07-13 22:31 UTCEPSS rescore
  6. 2026-07-13 06:13 UTCEPSS rescore
  7. 2026-07-13 06:13 UTCEPSS rescore
  8. 2026-07-12 05:46 UTCEPSS rescore
  9. 2026-07-10 20:39 UTCEG score recompute
  10. 2026-07-10 20:37 UTCMITRE cvelistV5first tracked

Related CVEs(same vendor + 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, with the most recent update on July 13, 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 0% probability of exploitation in the next 30 days, which ranks it in the top 64.5% of all scored CVEs.
What is the CVSS score of CVE-2026-57212?
CVE-2026-57212 has a CVSS v3 base score of 7.7 (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