RabbitMQ is a widely deployed enterprise messaging broker; an attacker can induce cluster-wide OAuth/JWT authentication outages, disrupting applications and services.
CVE-2026-67409
RabbitMQ JWKS fetch ignores HTTP status, causing persistent OAuth/JWT authentication DoS.
do firstUpgrade to a fixed release: 3.13.18, 4.0.23, 4.1.14, 4.2.9 (+1 more below).
Is CVE-2026-67409 being exploited?
Not confirmed. CVE-2026-67409 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.42% probability of exploitation in the next 30 days.
How severe is CVE-2026-67409?
CVE-2026-67409 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-67409?
Yes. A fix has been recorded for CVE-2026-67409. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-67409 affect?
CVE-2026-67409 affects RabbitMQ Server 3.13.0–3.13.17, RabbitMQ Server 4.0.0–4.0.22, 4.1.0–4.1.13, 4.2.0–4.2.8, 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-67409?
Upgrade to fixed versions (see advisory) and monitor JWKS responses; validate JWKS endpoint availability.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Persistent authentication denial-of-service: JWKS error responses wipe cached signing keys, blocking all OAuth2/JWT auth until a successful refresh.
Patch when possible
- affected>= 3.13.0 and < 3.13.18
- affected>= 4.0.0 and < 4.0.23
- affected>= 4.1.0 and < 4.1.14
- 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
- affected>= 4.1.0 and < 4.1.14
- affected>= 4.0.0 and < 4.0.23
- affected>= 3.13.0 and < 3.13.18
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-qw3h-qqm9-jrw8
- 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.