CVE-2026-67409 rabbitmq CVE debrief

Who should care

RabbitMQ administrators and users with OAuth2 and JWT authentication configured should assess exposure and apply patches or workarounds. Defenders should prioritize verifying exposure and applying patches or workarounds due to potential DoS impact on OAuth2 and JWT authentication configurations in RabbitMQ. RabbitMQ instances with OAuth2 and JWT authentication are potentially impacted by this vulnerability.

Why it matters

Defenders should prioritize verifying exposure and applying patches or workarounds due to potential DoS impact on OAuth2 and JWT authentication configurations in RabbitMQ.

• Potential persistent authentication denial of service (DoS) for OAuth2 and JWT users
• Amplification of attack impact due to single attacker affecting all legitimate users
• Verification priority for RabbitMQ instances with OAuth2 and JWT authentication

Technical summary

The uaajwt.erl module in RabbitMQ ignores HTTP response status codes when fetching JWKS keys, causing potential DoS via key destruction. Affected versions include 3.13.0 until 4.3.3, 4.2.9, 4.1.14, 4.0.23, and 3.13.18. The vulnerability is caused by the uaajwt.erl module ignoring HTTP response status codes when fetching JWKS keys, leading to potential DoS via key destruction. RabbitMQ administrators and users with OAuth2 and JWT authentication configured should assess exposure and apply patches or workarounds. The Erlang httpc module returns {ok, {{HttpVersion, StatusCode, ReasonPhrase}, Headers, Body}}.

Defensive priority

Defenders should prioritize verifying exposure and applying patches or workarounds, focusing on OAuth2 and JWT authentication configurations.

Recommended defensive actions

• Verify if RabbitMQ instances are exposed to untrusted networks or users
• Check if OAuth2 and JWT authentication are in use
• Apply patches or workarounds to affected versions
• Monitor for suspicious HTTP requests to JWKS endpoints
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability is caused by the uaajwt.erl module ignoring HTTP response status codes when fetching JWKS keys, leading to potential DoS via key destruction. The uaajwt.erl module in RabbitMQ ignores HTTP response status codes when fetching JWKS keys, causing potential DoS via key destruction. Affected versions include 3.13.0 until 4.3.3, 4.2.9, 4.1.14, 4.0.23, and 3.13.18. The Erlang httpc module returns {ok, {{HttpVersion, StatusCode, ReasonPhrase}, Headers, Body}}. The pattern {ok, {, , JwksBody}} matches ANY successful HTTP The

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.