All vulnerabilities

Servers and applications

CVE-2026-67411

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

Severity
Medium 6.0
Published
23 Jul 2026
Last changed
8 Oct 2026
Added to UpHeron
1 Nov 2026
Fixed in
3.13.18, 4.0.23, 4.1.14, 4.2.9, 4.3.3
Exploit chance
0.3% in the next 30 daysHigher than 25% of CVEs. EPSS by FIRST, 19 Nov 2026
Weakness
Incorrect authorization (CWE-863)
Attack
Over the network · Only under certain conditions · Needs a user account · No user action needed
Attacker can
Read data
CVSS vector
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Also known as
GHSA-4r6f-9cpw-f6g6
Sources
NVD, Project advisories (GitHub)

Description

Title: (Web) MQTT PROXY Protocol path bypasses loopback-only user restriction

RabbitMQ (Web) MQTT loses the PROXY Protocol-derived client address before the MQTT authentication path checks loopback_users. A remote client with valid credentials for a loopback-restricted account can therefore authenticate through a trusted PROXY Protocol frontend because the backend evaluates the frontend's 127.0.0.1 address instead of the original client address.

When rabbitmq_web_mqtt runs behind a trusted TCP frontend with web_mqtt.proxy_protocol = true, Cowboy preserves the original client address in a rabbit_proxy_socket. rabbit_web_mqtt_handler uses that wrapper for connection logging, but unwraps it before invoking rabbit_mqtt_processor:init/4. The processor then derives PeerIp from the raw frontend-to-backend socket and passes 127.0.0.1 to the loopback-user check.

From rabbitmq/rabbitmq-server's security advisory. Shortened; the full text is there.

Workarounds

One or multiple of:

  • Override default user's username, use a generated password (a recommended practice)
  • Adopt OAuth 2 or x.509 certificates for authentication instead of username/password pairs
  • Disable Proxy Protocol use
  • Disable the Web MQTT, MQTT plugins
Workarounds as given by rabbitmq/rabbitmq-server's security advisory.

Affected software

SoftwareAffected versions
RabbitMQServers and applications · cpe:a:broadcom:rabbitmq_server
  • From 3.13.0 before 3.13.18
  • From 4.0.0 before 4.0.23
  • From 4.1.0 before 4.1.14
  • From 4.2.0 before 4.2.9
  • From 4.3.0 before 4.3.3
RabbitMQServers and applications · github:rabbitmq/rabbitmq-server
  • From 3.13.0 before 3.13.18
  • From 4.0.0 before 4.0.23
  • From 4.1.0 before 4.1.14
  • From 4.2.0 before 4.2.9
  • From 4.3.0 before 4.3.3

About RabbitMQ

open source message broker, sometimes referred to as "Rabbit"

From Wikidata, CC0 1.0.
Docker Hub pulls
3,918,841,187Docker Hub, 15 Nov 2026
GitHub stars
13,973GitHub, 15 Nov 2026
Forks
4,032GitHub, 15 Nov 2026
Latest release
v4.4.0GitHub, 15 Nov 2026
Released
19 Oct 2026GitHub
Developer
Jean-Sébastien PédronWikidata
License
Mozilla Public License, version 2.0Wikidata
Written in
ErlangWikidata
First published on GitHub
20 Sept 2010GitHub

Release lines

ReleaseLatestSecurity fixes
4.44.4.0Until 31 Jul 2027
4.34.3.7Until 31 Jan 2027
4.24.2.9Ended 31 Jul 2026
4.14.1.8Ended 30 Jan 2026
4.04.0.9Ended 30 Apr 2025
3.133.13.7Ended 30 Sept 2024

From endoflife.date.

References

  • NVD https://nvd.nist.gov/vuln/detail/CVE-2026-67411
  • CVE.org https://www.cve.org/CVERecord?id=CVE-2026-67411
  • GitHub Advisory Database https://github.com/advisories/GHSA-4r6f-9cpw-f6g6
  • github.com https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-4r6f-9cpw-f6g6