CVE-2026-67404

RabbitMQ: OAuth2 silent verify_none fallback for JWKS fetch

State
Published
Severity
9.2 Critical
Published
Sep 23, 2026
Updated
Sep 29, 2026
Reserved
Jul 29, 2026

Read the record on cve.org

Description

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.

Scores

CVSSScoreVectorSource
4.09.2 CriticalCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NGitHub_M

Weaknesses

  • CWE-295 Improper Certificate Validation

Affected Products

ProductVersions
rabbitmq-serverrabbitmq
  • >= 3.13.0, < 3.13.15Affected
  • >= 4.0.0, < 4.0.20Affected
  • >= 4.1.0, < 4.1.11Affected
  • >= 4.2.0, < 4.2.6Affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.