CVE-2026-67404

What it is

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.

At a glance

Exploitability

Can be exploited over the network without logging in. High risk of data exposure, data tampering, service disruption.

Exploit odds

0.2% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-09-23 21:17 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-10-19 20:39 UTC Last updatedMost recent change to the record

Details

Published

2026-09-23 21:17 UTC

Last modified

2026-10-19 20:39 UTC

Exploit probability

0.2% · EPSS, next 30 days

Weakness

CWE-295 · Improper certificate validation

Record status

Analyzed

Affected

• Broadcom Rabbitmq Server < 3.13.15
• Broadcom Rabbitmq Server < 4.0.20
• Broadcom Rabbitmq Server < 4.1.11
• Broadcom Rabbitmq Server < 4.2.6

Attack profile CVSS 4.0 · 9.2

Attack vector

Network

Complexity

Low

Attack requirements

Present

Privileges needed

None

User interaction

None

Confidentiality

High

Integrity

High

Availability

High