rabbitmq-server — security advisory
RabbitMQ is a messaging and streaming broker. Prior to versions 4.0.22, 4.1.11, 4.2.6, and 4.3.0, accept_content/2 at line 56 calls rabbit_stream_manager:create_super_stream/... directly after is_authorized (which only checks the management tag + vhost access via is_authorized_vhost). The stream-protocol equivalent (rabbit_stream_reader.erl create_super_stream handler) calls rabbit_stream_utils:check_super_stream_management_permitted/4 which enforces configure on the exchange and each partition queue. The HTTP handler omits this call entirely. A user with management tag and vhost access , but no configure permission on any resource , can create super-streams (an exchange + N partition stream queues + bindings) via the HTTP API. The native stream-protocol path enforces configure on each resource; the HTTP path does not, creating a privilege escalation from 'can view' to 'can create persistent cluster-wide resources.' Preconditions include rabbitmq_stream_management plugin enabled management tag + vhost access (no resource permissions needed). This issue is fixed in versions 4.0.22, 4.1.11, 4.2.6, and 4.3.0.
- Products
- rabbitmq-server
- Affected versions
- 4.0.5-10, 4.0.5-11, 4.0.5-12, 4.0.5-13, 4.0.5-14, 4.0.5-6, 4.0.5-6+deb13u1, 4.0.5-6+deb13u2, 4.0.5-8, 4.0.5-9, 4.3.0-1, 4.3.0-2, 4.3.0-3, 4.3.2-1, 4.3.2-2, 4.3.2-3, 4.3.2-4, 4.3.2-5, 4.3.6-1
- Fixed versions
- 4.3.0-2
- CVEs
- CVE-2026-67218
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 1 Nov 2026, 01:48 UTC · Revision 1
Source evidence
RabbitMQ is a messaging and streaming broker. Prior to versions 4.0.22, 4.1.11, 4.2.6, and 4.3.0, accept_content/2 at line 56 calls rabbit_stream_manager:create_super_stream/... directly after is_authorized (which only checks the management tag + vhost access via is_authorized_vhost). The stream-protocol equivalent (rabbit_stream_reader.erl create_super_stream handler) calls rabbit_stream_utils:check_super_stream_management_permitted/4 which enforces configure on the exchange and each partition queue. The HTTP handler omits this call entirely. A user with management tag and vhost access , but no configure permission on any resource , can create super-streams (an exchange + N partition stream queues + bindings) via the HTTP API. The native stream-protocol path enforces configure on each resource; the HTTP path does not, creating a privilege escalation from 'can view' to 'can create persistent cluster-wide resources.' Preconditions include rabbitmq_stream_management plugin enabled management tag + vhost access (no resource permissions needed). This issue is fixed in versions 4.0.22, 4.1.11, 4.2.6, and 4.3.0.
osv:DEBIAN-CVE-2026-67218
rabbitmq-server
Fixed versions: Not specified
rabbitmq-server
Fixed versions: 4.3.0-2
Complete source record
{
"id": "432692830e67d861c94cc1308e11d66f8785d4bd9cbc7e56466e01ee07fb53fa",
"url": "https://osv.dev/vulnerability/DEBIAN-CVE-2026-67218",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "DEBIAN-CVE-2026-67218",
"summary": "RabbitMQ is a messaging and streaming broker. Prior to versions 4.0.22, 4.1.11, 4.2.6, and 4.3.0, accept_content/2 at line 56 calls rabbit_stream_manager:create_super_stream/... directly after is_authorized (which only checks the management tag + vhost access via is_authorized_vhost). The stream-protocol equivalent (rabbit_stream_reader.erl create_super_stream handler) calls rabbit_stream_utils:check_super_stream_management_permitted/4 which enforces configure on the exchange and each partition queue. The HTTP handler omits this call entirely. A user with management tag and vhost access , but no configure permission on any resource , can create super-streams (an exchange + N partition stream queues + bindings) via the HTTP API. The native stream-protocol path enforces configure on each resource; the HTTP path does not, creating a privilege escalation from 'can view' to 'can create persistent cluster-wide resources.' Preconditions include rabbitmq_stream_management plugin enabled management tag + vhost access (no resource permissions needed). This issue is fixed in versions 4.0.22, 4.1.11, 4.2.6, and 4.3.0.",
"evidence": "osv:DEBIAN-CVE-2026-67218",
"products": [
{
"name": {
"value": "rabbitmq-server",
"evidence": "/affected/0/package/name"
},
"prerequisites": [],
"fixed_versions": [],
"affected_versions": [
{
"value": "4.0.5-10",
"evidence": "/affected/0/versions"
},
{
"value": "4.0.5-11",
"evidence": "/affected/0/versions"
},
{
"value": "4.0.5-12",
"evidence": "/affected/0/versions"
},
{
"value": "4.0.5-13",
"evidence": "/affected/0/versions"
},
{
"value": "4.0.5-14",
"evidence": "/affected/0/versions"
},
{
"value": "4.0.5-6",
"evidence": "/affected/0/versions"
},
{
"value": "4.0.5-6+deb13u1",
"evidence": "/affected/0/versions"
},
{
"value": "4.0.5-6+deb13u2",
"evidence": "/affected/0/versions"
},
{
"value": "4.0.5-8",
"evidence": "/affected/0/versions"
},
{
"value": "4.0.5-9",
"evidence": "/affected/0/versions"
},
{
"value": "4.3.0-1",
"evidence": "/affected/0/versions"
},
{
"value": "4.3.0-2",
"evidence": "/affected/0/versions"
},
{
"value": "4.3.0-3",
"evidence": "/affected/0/versions"
},
{
"value": "4.3.2-1",
"evidence": "/affected/0/versions"
},
{
"value": "4.3.2-2",
"evidence": "/affected/0/versions"
},
{
"value": "4.3.2-3",
"evidence": "/affected/0/versions"
},
{
"value": "4.3.2-4",
"evidence": "/affected/0/versions"
},
{
"value": "4.3.2-5",
"evidence": "/affected/0/versions"
},
{
"value": "4.3.6-1",
"evidence": "/affected/0/versions"
}
]
},
{
"name": {
"value": "rabbitmq-server",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "4.3.0-2",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": [
{
"value": "4.0.5-10",
"evidence": "/affected/1/versions"
},
{
"value": "4.0.5-11",
"evidence": "/affected/1/versions"
},
{
"value": "4.0.5-12",
"evidence": "/affected/1/versions"
},
{
"value": "4.0.5-13",
"evidence": "/affected/1/versions"
},
{
"value": "4.0.5-14",
"evidence": "/affected/1/versions"
},
{
"value": "4.0.5-6",
"evidence": "/affected/1/versions"
},
{
"value": "4.0.5-8",
"evidence": "/affected/1/versions"
},
{
"value": "4.0.5-9",
"evidence": "/affected/1/versions"
},
{
"value": "4.3.0-1",
"evidence": "/affected/1/versions"
}
]
}
],
"severity": "medium",
"structured": {
"id": "DEBIAN-CVE-2026-67218",
"aliases": [
"DEBIAN-CVE-2026-67218"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H"
}
],
"affected": [
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
}
]
}
],
"package": {
"name": "rabbitmq-server",
"purl": "pkg:deb/debian/rabbitmq-server?arch=source&distro=trixie",
"ecosystem": "Debian:13"
},
"versions": [
"4.0.5-10",
"4.0.5-11",
"4.0.5-12",
"4.0.5-13",
"4.0.5-14",
"4.0.5-6",
"4.0.5-6+deb13u1",
"4.0.5-6+deb13u2",
"4.0.5-8",
"4.0.5-9",
"4.3.0-1",
"4.3.0-2",
"4.3.0-3",
"4.3.2-1",
"4.3.2-2",
"4.3.2-3",
"4.3.2-4",
"4.3.2-5",
"4.3.6-1"
],
"database_specific": {
"source": "https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2026-67218.json"
},
"ecosystem_specific": {
"urgency": "not yet assigned"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"fixed": "4.3.0-2"
}
]
}
],
"package": {
"name": "rabbitmq-server",
"purl": "pkg:deb/debian/rabbitmq-server?arch=source&distro=forky",
"ecosystem": "Debian:14"
},
"versions": [
"4.0.5-10",
"4.0.5-11",
"4.0.5-12",
"4.0.5-13",
"4.0.5-14",
"4.0.5-6",
"4.0.5-8",
"4.0.5-9",
"4.3.0-1"
],
"database_specific": {
"source": "https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2026-67218.json"
},
"ecosystem_specific": {
"urgency": "not yet assigned"
}
}
],
"modified": "2026-10-23T18:05:03.282014675Z",
"provider": "osv",
"upstream": [
"CVE-2026-67218"
],
"references": [
"https://security-tracker.debian.org/tracker/CVE-2026-67218"
]
},
"related_cves": [
{
"value": "CVE-2026-67218",
"evidence": "/upstream"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 424251,
"published_at": "2026-09-23T21:16:59.93+00:00"
}