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.7%, top 49% 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: 1%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
1%
EPSS %ILE
51%
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

Vendor Advisories for CVE-2026-57212(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

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.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
rabbitmq-server3.10.8-1 ... 4.3.2-4 (38 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
rabbitmq-server3.10.8-1.1 ... 4.3.2-4 (27 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
rabbitmq-server4.0.5-10 ... 4.3.2-4 (17 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
rabbitmq-server4.0.5-10 ... 4.3.0-1 (9 versions)4.3.0-2—

Weakness Classification(1)

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

Data Freshness Timeline

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

Showing the most recent 100 of 149 total refreshes for this CVE.

  1. 2026-08-30 06:14 UTCEG score recompute
  2. 2026-08-30 06:14 UTCVendor advisory
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-28 21:42 UTCEPSS rescore
  5. 2026-08-27 21:40 UTCEG score recompute
  6. 2026-08-27 21:40 UTCVendor advisory
  7. 2026-08-27 14:25 UTCEPSS rescore
  8. 2026-08-27 00:46 UTCEG score recompute
  9. 2026-08-27 00:46 UTCVendor advisory
  10. 2026-08-26 14:46 UTCEPSS rescore
  11. 2026-08-26 03:33 UTCEG score recompute
  12. 2026-08-26 03:33 UTCVendor advisory
  13. 2026-08-25 13:49 UTCEPSS rescore
  14. 2026-08-25 09:49 UTCVendor advisory
  15. 2026-08-24 20:14 UTCEG score recompute
  16. 2026-08-24 20:14 UTCVendor advisory
  17. 2026-08-24 06:28 UTCVendor advisory
  18. 2026-08-23 18:03 UTCVendor advisory
  19. 2026-08-23 05:45 UTCEG score recompute
  20. 2026-08-23 05:45 UTCVendor advisory
  21. 2026-08-23 00:19 UTCEPSS rescore
  22. 2026-08-22 17:28 UTCVendor advisory
  23. 2026-08-22 04:42 UTCEG score recompute
  24. 2026-08-22 04:42 UTCVendor advisory
  25. 2026-08-21 23:49 UTCEPSS rescore
Show 75 more
  1. 2026-08-21 16:04 UTCVendor advisory
  2. 2026-08-21 03:44 UTCEG score recompute
  3. 2026-08-21 03:44 UTCVendor advisory
  4. 2026-08-20 22:55 UTCEPSS rescore
  5. 2026-08-20 15:11 UTCVendor advisory
  6. 2026-08-20 01:32 UTCEG score recompute
  7. 2026-08-20 01:32 UTCVendor advisory
  8. 2026-08-19 17:04 UTCEPSS rescore
  9. 2026-08-19 09:16 UTCVendor advisory
  10. 2026-08-18 20:33 UTCEG score recompute
  11. 2026-08-18 20:33 UTCVendor advisory
  12. 2026-08-18 13:48 UTCEPSS rescore
  13. 2026-08-18 02:51 UTCEG score recompute
  14. 2026-08-18 02:51 UTCVendor advisory
  15. 2026-08-17 13:47 UTCEPSS rescore
  16. 2026-08-17 13:20 UTCVendor advisory
  17. 2026-08-17 01:03 UTCEG score recompute
  18. 2026-08-17 01:03 UTCVendor advisory
  19. 2026-08-16 14:56 UTCEPSS rescore
  20. 2026-08-16 12:46 UTCEG score recompute
  21. 2026-08-16 12:46 UTCVendor advisory
  22. 2026-08-16 02:14 UTCEPSS rescore
  23. 2026-08-16 00:29 UTCVendor advisory
  24. 2026-08-15 12:12 UTCEG score recompute
  25. 2026-08-15 12:12 UTCVendor advisory
  26. 2026-08-15 01:30 UTCEPSS rescore
  27. 2026-08-14 23:55 UTCVendor advisory
  28. 2026-08-14 11:38 UTCVendor advisory
  29. 2026-08-13 23:21 UTCEG score recompute
  30. 2026-08-13 23:21 UTCVendor advisory
  31. 2026-08-13 22:00 UTCEPSS rescore
  32. 2026-08-13 11:04 UTCVendor advisory
  33. 2026-08-12 22:47 UTCEG score recompute
  34. 2026-08-12 22:47 UTCVendor advisory
  35. 2026-08-12 13:51 UTCEPSS rescore
  36. 2026-08-12 10:30 UTCVendor advisory
  37. 2026-08-11 22:13 UTCEG score recompute
  38. 2026-08-11 22:13 UTCVendor advisory
  39. 2026-08-11 09:56 UTCEG score recompute
  40. 2026-08-11 09:56 UTCVendor advisory
  41. 2026-08-11 00:00 UTCEPSS rescore
  42. 2026-08-10 21:39 UTCVendor advisory
  43. 2026-08-10 09:22 UTCVendor advisory
  44. 2026-08-09 21:04 UTCEG score recompute
  45. 2026-08-09 21:04 UTCVendor advisory
  46. 2026-08-09 13:46 UTCEPSS rescore
  47. 2026-08-09 08:48 UTCVendor advisory
  48. 2026-08-08 20:31 UTCEG score recompute
  49. 2026-08-08 20:31 UTCVendor advisory
  50. 2026-08-08 16:37 UTCEPSS rescore
  51. 2026-08-08 08:14 UTCVendor advisory
  52. 2026-08-07 19:57 UTCEG score recompute
  53. 2026-08-07 19:57 UTCVendor advisory
  54. 2026-08-07 07:40 UTCVendor advisory
  55. 2026-08-06 19:23 UTCEG score recompute
  56. 2026-08-06 19:23 UTCVendor advisory
  57. 2026-08-06 13:47 UTCEPSS rescore
  58. 2026-08-06 07:06 UTCEG score recompute
  59. 2026-08-06 07:06 UTCVendor advisory
  60. 2026-08-05 19:17 UTCEPSS rescore
  61. 2026-08-05 18:49 UTCVendor advisory
  62. 2026-08-05 06:32 UTCVendor advisory
  63. 2026-08-04 18:12 UTCEG score recompute
  64. 2026-08-04 18:12 UTCVendor advisory
  65. 2026-08-04 15:10 UTCEPSS rescore
  66. 2026-08-04 10:39 UTCEPSS rescore
  67. 2026-08-04 05:44 UTCVendor advisory
  68. 2026-08-03 17:27 UTCEG score recompute
  69. 2026-08-03 17:27 UTCVendor advisory
  70. 2026-08-03 10:36 UTCEPSS rescore
  71. 2026-08-03 04:52 UTCVendor advisory
  72. 2026-08-02 16:35 UTCVendor advisory
  73. 2026-08-02 04:18 UTCEG score recompute
  74. 2026-08-02 04:18 UTCVendor advisory
  75. 2026-08-02 02:27 UTCEPSS rescore

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 1% probability of exploitation in the next 30 days, which ranks it in the top 48.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

See which npm, PyPI, Go, and Maven packages are affected by 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