rabbitmq-server
Affected
- introduced
0(ecosystem)
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: CVE-2026-67411
The record has no summary.
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.
High Basis: CVSS v3 score 7.1, vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
0 (ecosystem)None listed
No fixed version is listed.
0 (ecosystem)None listed
No fixed version is listed.
0, fixed 4.3.6-1 (ecosystem)4.3.6-1
4.3.6-1sudo apt-get update && sudo apt-get upgradeThis command upgrades the distribution's packages. Compare the fixed version with the version you have installed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: Debian Security Tracker (converted by OSV.dev)
Debian Security Tracker, converted to OSV by OSV.dev.