Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%
Buy Us a Coffee

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

Quick assessment

Affected
rabbitmq rabbitmq-server
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

RabbitMQ 是一个消息代理和流媒体处理系统。在版本 3.13.0 至 3.13.18、4.0.23、4.1.14、4.2.9 和 4.3.3 之间（包括这些版本边界），存在“JWKS 获取时忽略 HTTP 响应状态码导致签名密钥销毁从而引发认证拒绝服务”的安全漏洞（CWE-252）。 在文件 中，JWKS 密钥获取机制在从 OAuth2 提供商的 JWKS 端点下载签名密钥时，未对 HTTP 响应状态码进行验证。非 200 状态码的响应（包括 4xx 客户端错误和 5xx 服务器错误）被当作成功响应来处理。当

CVSS 8.2 · High EPSS 0.49% · P40
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-67409

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
RabbitMQ: JWKS Fetch Ignores HTTP Response Status Code - Signing Key Destruction Causes Authentication DoS
Source: CVE Program / CVE List V5
Vulnerability 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.
Source: CVE Program / CVE List V5
CVSS Information
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
Source: CVE Program / CVE List V5
Vulnerability Type
未加检查的返回值
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
rabbitmq rabbitmq-server >= 4.3.0, < 4.3.3 -

II. Public POCs for CVE-2026-67409

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-67409

请登录查看更多情报信息。

Other References for CVE-2026-67409 (3)

Same Patch Batch · rabbitmq · 2026-09-25 · 28 CVEs total

CVE-2026-67236 8.2 HIGH RabbitMQ: Plaintext username:password stored in an insecure cookie after successful POST /
CVE-2026-67410 8.2 HIGH RabbitMQ: OAuth2 Client Secret Exposed via Unauthenticated JavaScript Endpoint
CVE-2026-67239 7.6 HIGH RabbitMQ: Stored XSS via TLS peer-certificate DN in stream-management UI
CVE-2026-67237 7.5 HIGH RabbitMQ: Reflected XSS via the OAuth bootstrap JS endpoint
CVE-2026-67408 7.1 HIGH RabbitMQ: Stream Management Super-Stream Binding Keys Allocation Allows Low-Privilege Node
CVE-2026-67419 7.1 HIGH RabbitMQ: Consecutive topic wildcards cause combinatorial routing work
CVE-2026-67226 6.9 MEDIUM RabbitMQ: Admin-only atom exhaustion: PUT /api/users tags list
CVE-2026-61837 6.3 MEDIUM RabbitMQ: AMQP 1.0 management `GET /bindings` exposes full binding topology to any authent
CVE-2026-67242 6.3 MEDIUM RabbitMQ: OAuth2 is_integer(Exp) guard skips token-expiry checks for float exp
CVE-2026-67230 6.3 MEDIUM RabbitMQ: Web-STOMP unbounded pre-auth accumulation
CVE-2026-67223 6.3 MEDIUM RabbitMQ: LDAP DN injection via unescaped substitution
CVE-2026-67225 6.3 MEDIUM RabbitMQ: Stream-protocol frame length never validated against frame_max
CVE-2026-66073 6.0 MEDIUM RabbitMQ: Atom table exhaustion via management API node field
CVE-2026-66071 6.0 MEDIUM RabbitMQ: Atom exhaustion: OAuth2 JWT tag: scope values
CVE-2026-67413 6.0 MEDIUM RabbitMQ: Authenticated RabbitMQ JMS Topic Selector Users Can Consume Broker CPU with an U
CVE-2026-67412 6.0 MEDIUM RabbitMQ: Federation upstream skips vhost authorization allowing cross-vhost message acces
CVE-2026-67411 6.0 MEDIUM RabbitMQ: Web MQTT with PROXY Protocol enabled: a loopback-only user permission bypass
CVE-2026-67222 5.9 MEDIUM RabbitMQ: list_to_atom on auth_mechanism URI tokens in amqp_client
CVE-2026-67227 5.9 MEDIUM RabbitMQ: Atom exhaustion: to_atom on global-parameter :name
CVE-2026-67415 5.9 MEDIUM RabbitMQ: Shovel Management Atom Exhaustion Allows Persistent Broker-Wide Denial of Servic

Showing top 20 of 28 CVEs. View all on vendor page &rarr; →

IV. Related Vulnerabilities

Same product: rabbitmq-server
Same vendor: rabbitmq
Same weakness: CWE-252

V. Comments for CVE-2026-67409

No comments yet

Leave a comment