CVE-2026-67421Medium· 4.5▾ SunlitRabbitMQ 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 OAu…
▾ Sunlit zone — Low / medium · no exploitation signal
impact 24.8 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
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.
Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-67420Low· 2.3RabbitMQ is a messaging and streaming broker
CVE-2026-66078Low· 2.1RabbitMQ is a messaging and streaming broker
CVE-2026-67241Medium· 4.8RabbitMQ is a messaging and streaming broker
CVE-2026-61837Medium· 6.3RabbitMQ is a messaging and streaming broker
CVE-2026-67407Medium· 5.1RabbitMQ is a messaging and streaming broker
CVE-2026-67419High· 7.1RabbitMQ is a messaging and streaming broker