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
do firstUpgrade to a fixed release: 4.2.9, 4.3.3.
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. EPSS currently estimates a 0.41% probability of exploitation in the next 30 days.
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.2.0 and < 4.2.9
- affected>= 4.3.0 and < 4.3.3
- affected>= 4.3.0 and < 4.3.3
- affected>= 4.2.0 and < 4.2.9
As published in the CVE Program record, and, for products that ship the affected component, in the advisory named beside them. 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.
cisa ssvc
- exploitation
- poc
- automatable
- no
- technical impact
- partial
Assessed by CISA 25 Sept 2026 (SSVC 2.0.3).
timeline
- 25 Sept 2026Published
- 25 Sept 2026CISA SSVC assessment: exploitation poc · same day later
- 25 Sept 2026CVE record last updated · same day later
- 26 Sept 2026Analysed by vulneraibility.com · 1 day later
also known as
- Linkgithub.com /rabbitmq/rabbitmq-server/security/advisories/GHSA-f9f2-q3jf-wfj3
- Linkgithub.com /rabbitmq/rabbitmq-server/commit/60a85d3605ebf94fd234497242812547d441d457
- Linkgithub.com /rabbitmq/rabbitmq-server/commit/869f800998334bb363f2ad046f58de9caedc409e
- Linkgithub.com /rabbitmq/rabbitmq-server/releases/tag/v4.2.9
- Linkgithub.com /rabbitmq/rabbitmq-server/releases/tag/v4.3.3
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- OSV: advisory aliases and downstream package versions
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.