RabbitMQ is a messaging and streaming broker. From 3.13.0 until 4.3.3, 4.2.9 , 4.1.14, 4.0.24, and 3.13.18, Federation upstream in RabbitMQ skips vhost authorization allowing cross-vhost message access. what the bug lets you do. A policymaker on one vhost reads and drains messages out of another vhost it has no permission on. With the default ack-mode the source messages are consumed (deleted), not copied. Why that should not 1. Federation validates the upstream URI without any vhost-access Cross-vhost message read/drain from a per-vhost policymaker, breaking vhost tenancy This issue is fixed in versions 4.3.3, 4.2.9 , 4.1.14, 4.0.24, and 3.13.18.
{
"cna_assigner": "GitHub_M",
"cwe_ids": [
"CWE-862"
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/67xxx/CVE-2026-67412.json",
"unresolved_ranges": [
{
"extracted_events": [
{
"range": [
{
"introduced": "4.1.0"
},
{
"fixed": "4.1.14"
},
{
"introduced": "4.0.0"
},
{
"fixed": "4.0.24"
},
{
"introduced": "3.13.0"
},
{
"fixed": "3.13.18"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StringRangeExpression"
}
]
}
]
}{
"extracted_events": [
{
"cpe": "cpe:2.3:a:broadcom:rabbitmq_server:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "4.2.0"
},
{
"fixed": "4.2.9"
}
],
"source": "CPE_RANGE"
},
{
"cpe": "cpe:2.3:a:broadcom:rabbitmq_server:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "4.3.0"
},
{
"fixed": "4.3.3"
}
],
"source": "CPE_RANGE"
},
{
"original_tag": "v4.2.9",
"range": [
{
"fixed": "47d6d6457c7d1a440daed643cb7d76bba313e79c"
}
],
"source": "REFERENCES_TAG"
},
{
"original_tag": "v4.3.3",
"range": [
{
"fixed": "1d284b2d2a1e2f845ad22b0d5ee38ec372d50802"
}
],
"source": "REFERENCES_TAG"
}
]
}