RabbitMQ is a widely used enterprise message broker; exposed OAuth2 client secrets enable token theft and client impersonation across deployments.
CVE-2026-67410
Unauthenticated endpoint exposes OAuth2 client secret in RabbitMQ Management UI
Is CVE-2026-67410 being exploited?
Not confirmed. CVE-2026-67410 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.
How severe is CVE-2026-67410?
CVE-2026-67410 is rated High with a CVSS score of 8.2. 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-67410?
Yes. A fix has been recorded for CVE-2026-67410. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-67410 affect?
CVE-2026-67410 affects RabbitMQ Management UI 4.2.0 - 4.2.8, RabbitMQ Management UI 4.3.0 - 4.3.2. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-67410?
Upgrade to 4.2.9 or 4.3.3 and restrict/ firewall management UI access
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attacker can retrieve OAuth2 client secret, complete auth-code flows, obtain tokens and impersonate clients on affected RabbitMQ deployments.
Immediate action required
- affected>= 4.3.0 and < 4.3.3
- affected>= 4.2.0 and < 4.2.9
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.