CVE-2026-57219
Unauthenticated disclosure of RabbitMQ OAuth client secret via obsolete API
Is CVE-2026-57219 being exploited?
Not confirmed. CVE-2026-57219 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 2.0% probability of exploitation in the next 30 days.
How severe is CVE-2026-57219?
CVE-2026-57219 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-57219?
Yes. A fix has been recorded for CVE-2026-57219. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-57219 affect?
CVE-2026-57219 affects RabbitMQ < 3.13.15, RabbitMQ < 4.0.20, RabbitMQ < 4.1.11, RabbitMQ < 4.2.6, and 1 further product or version. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-57219?
Upgrade to fixed versions and rotate OAuth client secrets
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated attackers can retrieve OAuth client secret, enabling token issuance, impersonation, and access to protected services.
Immediate action required
- affected>= 4.2.0 and < 4.2.6
- affected>= 4.1.0 and < 4.1.11
- affected>= 4.0.0 and < 4.0.21
- affected>= 3.13.0 and < 3.13.15
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.