CVE-2026-67404 PUBLISHED

RabbitMQ: OAuth2 silent verify_none fallback for JWKS fetch

Assigner: GitHub_M
Reserved: 29.07.2026 Published: 23.09.2026 Updated: 23.09.2026

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.

Metrics

CVSS Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
CVSS Score: 9.2

Product Status

Vendor rabbitmq
Product rabbitmq-server
Versions
  • Version >= 3.13.0, < 3.13.15 is affected
  • Version >= 4.0.0, < 4.0.20 is affected
  • Version >= 4.1.0, < 4.1.11 is affected
  • Version >= 4.2.0, < 4.2.6 is affected

References

Problem Types

  • CWE-295: Improper Certificate Validation CWE