CVE-2026-57219

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 2.0%, top 20% 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.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 2%CVSS: 7.5Exploit: Elevated riskExposed: 0

A fix is available — apply it.

RabbitMQ is a messaging and streaming broker. Prior to 3.13.15, 4.0.20, 4.1.11, and 4.2.6, the obsolete GET /api/auth endpoint can disclose the OAuth 2 client secret on RabbitMQ installations configured with management.oauth_client_secret, exposing credentials to unauthenticated callers when the management plugin and that OAuth configuration are enabled. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
50(Track)
EG Risk 50/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
Severity75% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
2%
EPSS %ILE
80%
KEV
Not listed

Published

July 10, 2026

Last Modified

July 29, 2026

Advisory Details (6)

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

Unauthenticated disclosure of OAuth client credentials via an HTTP API endpoint with certain less common OAuth 2 configurations · Advisory · rabbitmq/rabbitmq-server · GitHub

https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-pj24-8j6m-vq9q
github_release Patch Available

RabbitMQ 4.2.6

Patch available: rabbitmq/rabbitmq-server v4.2.6

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

Remove an endpoint that's fallen out of use (backport #16083) (backport #16084)

Fix merged in rabbitmq/rabbitmq-server PR #16086 on 2026-04-14 — awaiting tagged release

https://github.com/rabbitmq/rabbitmq-server/pull/16086
github_pr

Remove an endpoint that's fallen out of use

Fix merged in rabbitmq/rabbitmq-server PR #16083 on 2026-04-14 — awaiting tagged release

https://github.com/rabbitmq/rabbitmq-server/pull/16083
github_commit

commit aa387c4451e7 (rabbitmq/rabbitmq-server)

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

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

commit 98b1daf74023 (rabbitmq/rabbitmq-server)

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

https://github.com/rabbitmq/rabbitmq-server/commit/98b1daf740237c85941e8addcbea6e74f4a2743c

Vendor Advisories for CVE-2026-57219(3)

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-3-main-4.3.2-1.hum12026-07-06redhat
redhatrabbitmq-server4-2-main-4.2.8-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(2)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 65× 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 203 total refreshes for this CVE.

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

Publicly available exploits

(1 reference)

Working exploit code is in the public domain. Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Nucleihttp/cves/2026/CVE-2026-57219.yaml
    First seen Jan 1, 2026

    RabbitMQ Management - OAuth 2 Client Secret Disclosure

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-57219?
CVE-2026-57219 is a high vulnerability published on July 10, 2026. RabbitMQ is a messaging and streaming broker. Prior to 3.13.15, 4.0.20, 4.1.11, and 4.2.6, the obsolete GET /api/auth endpoint can disclose the OAuth 2 client secret on RabbitMQ installations configured with management.oauthclientsecret, exposing credentials to unauthenticated callers when the…
When was CVE-2026-57219 disclosed?
CVE-2026-57219 was first published in the National Vulnerability Database on July 10, 2026, with the most recent update on July 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-57219 actively exploited?
CVE-2026-57219 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2% probability of exploitation in the next 30 days, which ranks it in the top 20.3% of all scored CVEs.
What is the CVSS score of CVE-2026-57219?
CVE-2026-57219 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-57219?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-57219, 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-57219

Explore →

Is Your Infrastructure Affected by CVE-2026-57219?

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

Start Free Scan →Browse All CVEs