Authenticated MQTT access via discarded proxy address
Published Sep 25, 2026 · Updated Sep 25, 2026
Incorrect authorization in affected RabbitMQ Server releases allows remote authenticated users to bypass loopback-only MQTT account restrictions. The Web MQTT handler unwraps a proxy-aware socket before rabbit_mqtt_processor:init/4 derives PeerIp, so loopback_users evaluates the trusted frontend address instead of the original client. A reachable trusted PROXY Protocol frontend, enabled MQTT or Web MQTT, and valid credentials for a loopback-restricted account are required; password authentication remains enforced, while the account's permitted messages and resources become accessible.
Summary
What happened
Incorrect authorization in affected RabbitMQ Server releases allows remote authenticated users to bypass loopback-only MQTT account restrictions. The Web MQTT handler unwraps a proxy-aware socket before rabbit_mqtt_processor:init/4 derives PeerIp, so loopback_users evaluates the trusted frontend address instead of the original client. A reachable trusted PROXY Protocol frontend, enabled MQTT or Web MQTT, and valid credentials for a loopback-restricted account are required; password authentication remains enforced, while the account's permitted messages and resources become accessible.
The record
- CVE
- CVE-2026-67411
- Published
- Sep 25, 2026
- Updated
- Sep 25, 2026
- Vendor
- RabbitMQ
- Product
- RabbitMQ Server
- Classifications
- CWE-863, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 25, 2026CVE publishedPublication date reported by the CVE source.
- Sep 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 3.13.0, < 3.13.18
- Affected versionversion=>= 4.0.0, < 4.0.23
- Affected versionversion=>= 4.1.0, < 4.1.14
- Affected versionversion=>= 4.2.0, < 4.2.9
- Affected versionversion=>= 4.3.0, < 4.3.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Public exploit references
- Upstream Web MQTT PROXY Protocol verification proof of conceptfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started