RabbitMQ: Stored HTML Injection in RabbitMQ Management OAuth Error Handling
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.
- Products
- rabbitmq
- Affected versions
- Not specified
- Fixed versions
- 3.13.19, 4.0.24, 4.1.15, 4.2.10, 4.3.5
- CVEs
- CVE-2026-67421
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 28 Oct 2026, 04:12 UTC · Revision 1
Source evidence
RabbitMQ: Stored HTML Injection in RabbitMQ Management OAuth Error Handling
core-osv · Original sourcePublished 1 Oct 2026, 09:34 UTC
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.
osv:BIT-rabbitmq-2026-67421
rabbitmq
Fixed versions: 3.13.19, 4.0.24, 4.1.15, 4.2.10, 4.3.5
Complete source record
{
"id": "25c30c0568d6814cf6bc625dbbaea43ac1fd51cc9bb98748f84560bfe69bf7a2",
"url": "https://osv.dev/vulnerability/BIT-rabbitmq-2026-67421",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "RabbitMQ: Stored HTML Injection in RabbitMQ Management OAuth Error Handling",
"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.",
"evidence": "osv:BIT-rabbitmq-2026-67421",
"products": [
{
"name": {
"value": "rabbitmq",
"evidence": "/affected/0/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "3.13.19",
"evidence": "/affected/0/ranges"
},
{
"value": "4.0.24",
"evidence": "/affected/0/ranges"
},
{
"value": "4.1.15",
"evidence": "/affected/0/ranges"
},
{
"value": "4.2.10",
"evidence": "/affected/0/ranges"
},
{
"value": "4.3.5",
"evidence": "/affected/0/ranges"
}
],
"affected_versions": []
}
],
"severity": "medium",
"structured": {
"id": "BIT-rabbitmq-2026-67421",
"aliases": [
"BIT-rabbitmq-2026-67421",
"CVE-2026-67421",
"GHSA-6256-27fm-4rgr"
],
"affected": [
{
"ranges": [
{
"type": "SEMVER",
"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"
},
{
"introduced": "4.3.0"
},
{
"fixed": "4.3.5"
}
]
}
],
"package": {
"name": "rabbitmq",
"purl": "pkg:bitnami/rabbitmq",
"ecosystem": "Bitnami"
},
"severity": [
{
"type": "CVSS_V4",
"score": "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:A/VC:L/VI:L/VA:N/SC:H/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X"
}
],
"database_specific": {
"source": "https://github.com/bitnami/vulndb/tree/main/data/rabbitmq/BIT-rabbitmq-2026-67421.json"
}
}
],
"modified": "2026-10-07T14:30:05.097261408Z",
"provider": "osv",
"references": [
"https://github.com/rabbitmq/rabbitmq-server/commit/ff595eaaa6d4f580f72fa04801ffd35f48c46027",
"https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.5",
"https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-6256-27fm-4rgr",
"https://nvd.nist.gov/vuln/detail/CVE-2026-67421"
],
"provider_metadata": {
"cpes": [
"cpe:2.3:a:vmware:rabbitmq:*:*:*:*:*:*:*:*"
],
"severity": "Medium"
}
},
"related_cves": [
{
"value": "CVE-2026-67421",
"evidence": "/aliases"
}
],
"security_relevant": true,
"severity_evidence": "/database_specific/severity"
},
"source_id": "core-osv",
"document_id": 95089,
"published_at": "2026-10-01T09:34:00.722+00:00"
}