CVE-2026-67409
Description
A flaw was found in rabbitmq-server. When retrieving cryptographic signing keys from an identity provider's JSON Web Key Set (JWKS) endpoint, the server fails to validate HTTP response status codes. If an error response is returned with valid JSON lacking key data, all previously cached signing keys are purged. This allows an attacker to cause a persistent Denial of Service (DoS) by preventing all legitimate users from authenticating.
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.
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.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 7.5 | 6.5 | N/A |
| Attack Vector | Network | Network | N/A |
| Attack Complexity | Low | Low | N/A |
| Privileges Required | None | Low | N/A |
| User Interaction | None | None | N/A |
| Scope | Unchanged | Unchanged | N/A |
| Confidentiality | None | None | N/A |
| Integrity Impact | None | None | N/A |
| Availability Impact | High | High | N/A |
Vector
Red Hat: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Understanding the Weakness (CWE)
Availability,Integrity
Technical Impact: Unexpected State; Varies by Context; DoS: Crash, Exit, or Restart
The product could be prevented from detecting unexpected states and conditions, placing the product into a state that could lead to a crash or other unintended behaviors.
Access Control
Technical Impact: Bypass Protection Mechanism
If the method/function is used for a protection mechanism, then an unchecked return value could prevent the code from being able to see if the protection mechanism fails. For example, if the program calls a function to drop privileges but does not check the return code to ensure that privileges were successfully dropped, then the program will continue to operate with the higher privileges.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.