CVEvulnerability

CVE-2026-67411

6.0 MEDIUM Published 2026-09-25 Modified 2026-10-08 Official page ↗
Status
Analyzed
Published
2026-09-25
Last modified
2026-10-08
Assigner
[email protected]
CVSS 4.0 ([email protected])
6.0 MEDIUM — 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
CVSS 3.1 ([email protected])
7.1 HIGH — CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
Weaknesses
CWE-863

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.

Affected configurations

• broadcom rabbitmq server (>= 3.13.0 < 3.13.18) • broadcom rabbitmq server (>= 4.0.0 < 4.0.23) • broadcom rabbitmq server (>= 4.1.0 < 4.1.14) • broadcom rabbitmq server (>= 4.2.0 < 4.2.9) • broadcom rabbitmq server (>= 4.3.0 < 4.3.3)

Related

Weakness · CWE (1)

  • CWE-863 Incorrect Authorization weakness

References