Reference page — cumulative record through Monday, October 19, 2026 UTC. Reference pages update as the archive grows; only dated daily editions are immutable pages of record.

CVE-2026-67409

CVE-2026-67409HIGH

RabbitMQ: JWKS Fetch Ignores HTTP Response Status Code - Signing Key Destruction Causes Authentication DoS

  AV  AC  AT  PR  UI  VC  VI  VA   CVSS    EPSS   %ile   KEV
   N   L   P   N   N   N   N   H    8.2   .0042   34.6     —

AFFECTED
  Product          Versions             Fixed
  rabbitmq-server  >= 4.3.0, < 4.3.3 –  —

TIMELINE
  Jul 29  Reserved by GitHub_M
  Sep 25  Published (CNA: GitHub_M)
  Oct 8   EXPLOIT PUBLISHED — CVE-2026-67409 (rabbitmq-server). Public exploit reference added.

CWE-252 · CNA: GitHub_M · CVSS v4.0 · 3 references · NVD status: Analyzed

Description

RabbitMQ is a messaging and streaming broker. From 3.13.0 until 4.3.3, 4.2.9, 4.1.14, 4.0.23, and 3.13.18, JWKS Fetch Ignores HTTP Response Status Code - Signing Key Destruction Causes Authentication DoS (CWE-252). the JWKS key fetching mechanism in uaajwt.erl does not validate the HTTP response status code when downloading signing keys from the OAuth2 provider's JWKS endpoint. Non-200 responses (including 4xx and 5xx errors) are processed identically to successful responses. When the JWKS endpoint returns an error response with a valid-JSON body that lacks a keys field, all previously cached signing keys are destroyed, causing a persistent authentication denial of Files: deps/rabbitmqauthbackendoauth2/src/uaajwt.erl, lines 50-63 deps/rabbitmqauthbackendoauth2/src/uaajwks.erl, lines 5-7 deps/rabbitmqauthbackendoauth2/src/rabbitoauth2provider.erl, lines 98-107 Bug 1: HTTP status code ignored (uaajwt.erl:50-63): The Erlang httpc module returns {ok, {{HttpVersion, StatusCode, ReasonPhrase}, Headers, Body}}. The pattern {ok, {, , JwksBody}} matches ANY successful HTTP transaction Persistent authentication DoS: Once keys are destroyed, ALL OAuth2/JWT authentication fails for all users until a new successful JWKS refresh occurs Amplification: A single attacker can deny access to all legitimate OAuth2 users across the entire RabbitMQ. This issue is fixed in versions 4.3.3, 4.2.9, 4.1.14, 4.0.23, and 3.13.18.

Lifecycle

Complete event history — 3 events, chronological
Date	Event	Detail
July 29, 2026	Reserved	Reserved by GitHub_M
September 25, 2026	Published	Published (CNA: GitHub_M)
October 8, 2026	EXPLOIT PUBLISHED	EXPLOIT PUBLISHED — CVE-2026-67409 (rabbitmq-server). Public exploit reference added.

Affected

Affected products and packages — 1 row
Vendor	Product / Package	Ecosystem	Version introduced	Fixed
rabbitmq	rabbitmq-server	—	>= 4.3.0, < 4.3.3	—

Weaknesses

CWE-252

References (3)

https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.9 [Release Notes]
https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.3 [Release Notes]
https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-qw3h-qqm9-jrw8 [Exploit, Third Party Advisory]

Authoritative record: CVE-2026-67409 at cve.org

Vendors: rabbitmq

Weaknesses: CWE-252

About this page

This is a reference page, not a dated page of record. It assembles the complete lifecycle of CVE-2026-67409 from the CVE Program record, NVD enrichment, the CISA KEV catalog, EPSS, and OSV advisories. The box score's numbers (CVSS, EPSS, KEV status) are current as of Monday, October 19, 2026 UTC and are re-derived as the archive grows; only dated daily editions are immutable pages of record. The authoritative source for this identifier is cve.org.