Disclosure summary
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.
Source-reported weakness categories
CWE-862
Source-specific records & product guidance
Sources retain their own attribution and scoring. Follow the original record to confirm affected versions, fixed releases, and configuration conditions.
NIST National Vulnerability Database · NVD-CVE-2026-67421
Open original source · Updated Oct 06, 2026
Only CPE matches marked vulnerable=true are indexed. AND/OR platform conditions must be checked in the original NVD record.
| Vendor | Product / association | Version / bounds |
|---|---|---|
| broadcom | rabbitmq_server | * {"versionStartIncluding":"4.3.0","versionEndExcluding":"4.3.5"} |
Original records & references
- NIST NVD record
- CVE Program record
- github.com — Patch
- github.com — Release Notes
- github.com — Exploit, Vendor Advisory
- github.com — Exploit, Vendor Advisory
PUBLISHED 2026-09-25T13:17:14-04:00
MODIFIED 2026-10-06T15:53:05-04:00
INGESTED 2026-10-10T20:45:41-04:00