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.
{
"cna_assigner": "GitHub_M",
"cwe_ids": [
"CWE-863"
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/67xxx/CVE-2026-67411.json",
"unresolved_ranges": [
{
"extracted_events": [
{
"introduced": "4.1.0"
},
{
"fixed": "4.1.14"
},
{
"introduced": "4.0.0"
},
{
"fixed": "4.0.23"
},
{
"introduced": "3.13.0"
},
{
"fixed": "3.13.18"
}
],
"source": "AFFECTED_FIELD"
}
]
}