CVE-2026-67411

RabbitMQ: Web MQTT with PROXY Protocol enabled: a loopback-only user permission bypass

State
Published
Severity
6.0 Medium
Published
Sep 25, 2026
Updated
Sep 25, 2026
Reserved
Jul 29, 2026

Read the record on cve.org

Description

RabbitMQ is a messaging and streaming broker. From 3.13.0 until 3.13.18, 4.0.23, 4.1.14, 4.2.9, and 4.3.3, native MQTT and MQTT over WebSocket behind a trusted PROXY Protocol frontend could lose the proxy-derived client address before the MQTT authentication path checked loopback_users, causing the frontend-to-broker address to be treated as loopback. An attacker who can reach the trusted frontend and has valid credentials for a loopback-restricted account can therefore bypass the source-address restriction; the issue does not bypass password authentication. This issue is fixed in versions 3.13.18, 4.0.23, 4.1.14, 4.2.9, and 4.3.3.

Scores

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

Weaknesses

Affected Products

ProductVersions
rabbitmq-serverrabbitmq
  • >= 4.3.0, < 4.3.3Affected
  • >= 4.2.0, < 4.2.9Affected
  • >= 4.1.0, < 4.1.14Affected
  • >= 4.0.0, < 4.0.23Affected
  • >= 3.13.0, < 3.13.18Affected

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.