cve.bz

CVE-2026-67409 broadcom rabbitmq server: Unchecked Return Value

8.2 highExploit referenceEPSS 0.4%

High (8.2) in broadcom rabbitmq server. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 4.0

8.2 high
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 37th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-09-25. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-252 Unchecked Return Value
OWASP Top 10
A10:2025 Mishandling of Exceptional Conditions
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-67409 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-67409?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-67409?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-67409 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
broadcom:rabbitmq_serverfrom 3.13.0 before 3.13.18
broadcom:rabbitmq_serverfrom 4.0.0 before 4.0.23
broadcom:rabbitmq_serverfrom 4.1.0 before 4.1.14
broadcom:rabbitmq_serverfrom 4.2.0 before 4.2.9
broadcom:rabbitmq_serverfrom 4.3.0 before 4.3.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13rabbitmq-serverno fix listedDEBIAN-CVE-2026-67409
Debian14rabbitmq-server4.3.6-1DEBIAN-CVE-2026-67409
Ubuntu22.04:LTSrabbitmq-server3.9.27-0ubuntu0.6UBUNTU-CVE-2026-67409 USN-8933-1
Ubuntu24.04:LTSrabbitmq-server3.12.1-1ubuntu1.7UBUNTU-CVE-2026-67409 USN-8933-1
Ubuntu26.04:LTSrabbitmq-server4.0.5-10ubuntu5.2UBUNTU-CVE-2026-67409 USN-8933-1
Ubuntu26.10rabbitmq-serverno fix listedUBUNTU-CVE-2026-67409
UbuntuPro:16.04:LTSrabbitmq-server3.5.7-1ubuntu0.16.04.4+esm3UBUNTU-CVE-2026-67409 USN-8933-1
UbuntuPro:18.04:LTSrabbitmq-server3.6.10-1ubuntu0.5+esm1UBUNTU-CVE-2026-67409 USN-8933-1
UbuntuPro:20.04:LTSrabbitmq-server3.8.3-0ubuntu0.3+esm2UBUNTU-CVE-2026-67409 USN-8933-1
Red Hathummingbird:1rabbitmq-server4.30:4.3.6-1.hum1RHSA-2026:67552
Azure Linux3rabbitmq-server3.13.7-11AZL-109731

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat.

Red Hat

Red Hat rates this Important.

Red Hat's statement

A flaw was found in rabbitmq-server within the OAuth2 JWT authentication backend (uaajwt.erl). When querying an identity provider's JWKS endpoint for signing keys, the server fails to validate HTTP response status codes. An attacker capable of inducing or timing a JWKS fetch when the endpoint returns an HTTP error response containing valid JSON without a "keys" field causes the server to purge all cached signing keys. Consequently, all subsequent OAuth2/JWT authentication attempts fail, resulting in a persistent denial of service across the broker until valid keys are successfully refetched.

Red Hat's mitigation

Disable the rabbitmq_auth_backend_oauth2 plugin and transition to internal username/password or mutual TLS (mTLS) authentication. Alternatively, place a reverse proxy in front of the JWKS endpoint to drop or sanitize non-200 HTTP responses before they reach RabbitMQ.

ProductPackageStateAdvisory
Red Hat Hardened Imagesrabbitmq-server4-3-main-4.3.6-1.hum1Fixed 2026-09-15RHSA-2026:67552
Red Hat Hardened Imagesrabbitmq-server4.2Will not fix
Red Hat OpenStack Platform 13 (Queens)rabbitmq-serverNot affected
Red Hat OpenStack Platform 16.2rabbitmq-serverNot affected
Red Hat OpenStack Platform 17.1rabbitmq-serverNot affected
Red Hat OpenStack Platform 18.0rabbitmq-serverNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-67409.

References

Check your stackJSON