Is CVE-2026-67411 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-67411 being exploited in the wild.

How severe is CVE-2026-67411?

Informational severity, published 25 September 2026.

Which products and versions are affected?

RabbitMQ 3.13.0 to 3.13.17, 4.0.0 to 4.0.22, 4.1.0 to 4.1.13, 4.2.0 to 4.2.8, 4.3.0 to 4.3.2.

Is there a fix for CVE-2026-67411?

A patch was published on 2026-07-15: Fixes cherry-picked to maintenance branches; versions 3.13.18, 4.0.23, 4.1.14, 4.2.9, 4.3.3 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-67411 attacked?

It is attacked over the network, in a hosted service.

Am I affected by CVE-2026-67411?

Check whether you run RabbitMQ at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-67411: RabbitMQ MQTT loopback user bypass via PROXY Protocol

CVE-2026-67411 · Severity: info · Published 2026-09-25

RabbitMQ is a message broker that enterprises use for reliable message queuing and streaming. When deployed behind a PROXY Protocol frontend, the MQTT protocol handler could lose the client's real IP address before checking whether the connection is from a restricted loopback-only account. An attacker with valid credentials for such an account could bypass the source-address restriction and connect from the network, though password authentication is still required.

Technologies: RabbitMQ. Vendors: RabbitMQ.

Quick answers

Is CVE-2026-67411 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-67411 being exploited in the wild.
How severe is CVE-2026-67411?: Informational severity, published 25 September 2026.
Which products and versions are affected?: RabbitMQ 3.13.0 to 3.13.17, 4.0.0 to 4.0.22, 4.1.0 to 4.1.13, 4.2.0 to 4.2.8, 4.3.0 to 4.3.2.
Is there a fix for CVE-2026-67411?: A patch was published on 2026-07-15: Fixes cherry-picked to maintenance branches; versions 3.13.18, 4.0.23, 4.1.14, 4.2.9, 4.3.3 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-67411 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-67411?: Check whether you run RabbitMQ at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

RabbitMQ's native MQTT and WebSocket MQTT implementations fail to preserve the proxy-derived client address through the full authentication path, causing the loopback_users check to receive the frontend-to-broker address instead. An attacker with network access to the trusted PROXY Protocol frontend and valid credentials for a loopback-restricted user can bypass source-address restrictions. Password authentication is still enforced; this is a source-address bypass only.

Affected products

RabbitMQ RabbitMQ 3.13.0 to 3.13.17, 4.0.0 to 4.0.22, 4.1.0 to 4.1.13, 4.2.0 to 4.2.8, 4.3.0 to 4.3.2

Timeline

2026-09-25: disclosed
2026-07-15: patched: Fixes cherry-picked to maintenance branches; versions 3.13.18, 4.0.23, 4.1.14, 4.2.9, 4.3.3 released

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.