CVE-2026-67404

published 23 Sep 2026 · updated 25 Oct 2026

RabbitMQ: OAuth2 silent verify_none fallback for JWKS fetch

9.2CriticalCVSS 9.2EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.

RabbitMQ is a messaging and streaming broker. Prior to versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0, When no CA bundle is available, ssl_options/1 falls back to [{verify, verify_none}] with no warning. An attacker in a man-in-the-middle position can forge the JWKS response, which leads the broker to accept arbitrary JWTs. Preconditions include The OAuth2 plugin must be in use with no cacertfile configured and the OS CA bundle empty or unreadable (for example, in a minimal container), and the attacker must hold a network man-in-the-middle position.. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
rabbitmq>=3.13.0 <3.13.15, >=4.0.0 <4.0.20, >=4.1.0 <4.1.11, >=4.2.0 <4.2.6

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-67404 severity on Zeptric[![CVE-2026-67404](https://zeptric.io/badge/cve/CVE-2026-67404.svg)](https://zeptric.io/cve/CVE-2026-67404)