RabbitMQ is a messaging and streaming broker. From 3.13.0 until 3.13.19, 4.0.24, 4.1.15, 4.2.10, and 4.3.5, RabbitMQ Management rendered an AMQP authorization-error reason containing an attacker-controlled queue name as HTML when the OAuth management UI was enabled. Exploitation requires an attacker with queue configure permission, a management administrator who can see but cannot read that queue, and the administrator clicking Get Message(s). A queue name containing a base element can then retarget the automatic relative refresh because the Content Security Policy omits base-uri and connect-src, and an attacker endpoint that permits the management origin through CORS can receive the victim's Authorization header. This issue is fixed in versions 3.13.19, 4.0.24, 4.1.15, 4.2.10, and 4.3.5.
{
"cna_assigner": "GitHub_M",
"cwe_ids": [
"CWE-862"
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/67xxx/CVE-2026-67421.json",
"unresolved_ranges": [
{
"extracted_events": [
{
"introduced": "3.13.0"
},
{
"fixed": "3.13.19"
},
{
"introduced": "4.0.0"
},
{
"fixed": "4.0.24"
},
{
"introduced": "4.1.0"
},
{
"fixed": "4.1.15"
},
{
"introduced": "4.2.0"
},
{
"fixed": "4.2.10"
}
],
"source": "AFFECTED_FIELD"
}
]
}