CVE-2026-57219

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 72% 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 — 4 sources updated this week
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: 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.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)
EPSS
28.1%
KEV
Not listed

Published

July 10, 2026

Last Modified

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 24× 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.

  1. 2026-07-15 20:26 UTCEG score recompute
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-15 16:57 UTCEPSS rescore
  4. 2026-07-15 09:32 UTCEG score recompute
  5. 2026-07-15 02:00 UTCEPSS rescore
  6. 2026-07-15 02:00 UTCEPSS rescore
  7. 2026-07-14 22:37 UTCEG score recompute
  8. 2026-07-14 15:20 UTCNVD updateCVSS v3 → 7.5
  9. 2026-07-14 14:30 UTCMITRE cvelistV5CVSS v3 → 8.7
  10. 2026-07-14 11:44 UTCEG score recompute
  11. 2026-07-14 00:51 UTCEG score recompute▼ 1.20
  12. 2026-07-13 22:31 UTCEPSS rescore
  13. 2026-07-13 22:08 UTCNVD updateCVSS v3 → 7.5
  14. 2026-07-13 13:58 UTCEG score recompute
  15. 2026-07-13 06:13 UTCEPSS rescore
  16. 2026-07-13 06:13 UTCEPSS rescore
  17. 2026-07-13 03:04 UTCEG score recompute
  18. 2026-07-12 16:11 UTCEG score recompute
  19. 2026-07-12 05:46 UTCEPSS rescore
  20. 2026-07-12 05:17 UTCEG score recompute
  21. 2026-07-11 18:24 UTCEG score recompute
  22. 2026-07-11 07:31 UTCEG score recompute
  23. 2026-07-10 20:38 UTCEG score recompute
  24. 2026-07-10 20:37 UTCMITRE cvelistV5first tracked

Related CVEs(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 14, 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 28.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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

Explore the affected products and dependency analysis for 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