Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Fri, 25 Sep 2026 16:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | RabbitMQ: Web MQTT with PROXY Protocol enabled: a loopback-only user permission bypass | |
| Weaknesses | CWE-863 | |
| References |
|
|
| Metrics |
cvssV4_0
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-09-25T16:55:42.722Z
Reserved: 2026-07-29T15:02:20.412Z
Link: CVE-2026-67411
No data.
Status : Received
Published: 2026-09-25T17:17:13.237
Modified: 2026-09-25T17:17:13.237
Link: CVE-2026-67411
No data.
OpenCVE Enrichment
No data.
-
CWE-863
Incorrect Authorization