Skip to content
Heist/ feed
Back to feed
MediumFix available

RabbitMQ: Super-stream HTTP creation skips configure-permission check

Type: advisorySources: OSV

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
Affected versions
Not specified
Fixed versions
4.0.22, 4.1.11, 4.2.6
CVEs
CVE-2026-67218
Confirmed fixed CVEs
Not specified
Updated in this feed
31 Oct 2026, 09:34 UTC · Revision 1

Source evidence

RabbitMQ: Super-stream HTTP creation skips configure-permission check

core-osv · Original source

Published 1 Oct 2026, 09:33 UTC

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:BIT-rabbitmq-2026-67218

rabbitmq

Fixed versions: 4.0.22, 4.1.11, 4.2.6

Complete source record
{
  "id": "4ac862cab4bc04a25abbc32693822e1bf1779bde37e14efff9c65e27177c2b03",
  "url": "https://osv.dev/vulnerability/BIT-rabbitmq-2026-67218",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "RabbitMQ: Super-stream HTTP creation skips configure-permission check",
    "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:BIT-rabbitmq-2026-67218",
    "products": [
      {
        "name": {
          "value": "rabbitmq",
          "evidence": "/affected/0/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "4.0.22",
            "evidence": "/affected/0/ranges"
          },
          {
            "value": "4.1.11",
            "evidence": "/affected/0/ranges"
          },
          {
            "value": "4.2.6",
            "evidence": "/affected/0/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "medium",
    "structured": {
      "id": "BIT-rabbitmq-2026-67218",
      "aliases": [
        "BIT-rabbitmq-2026-67218",
        "CVE-2026-67218",
        "GHSA-34jw-rm7g-hph4"
      ],
      "affected": [
        {
          "ranges": [
            {
              "type": "SEMVER",
              "events": [
                {
                  "introduced": "4.0.0"
                },
                {
                  "fixed": "4.0.22"
                },
                {
                  "introduced": "4.1.0"
                },
                {
                  "fixed": "4.1.11"
                },
                {
                  "introduced": "4.2.0"
                },
                {
                  "fixed": "4.2.6"
                }
              ]
            }
          ],
          "package": {
            "name": "rabbitmq",
            "purl": "pkg:bitnami/rabbitmq",
            "ecosystem": "Bitnami"
          },
          "severity": [
            {
              "type": "CVSS_V3",
              "score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H"
            }
          ],
          "database_specific": {
            "source": "https://github.com/bitnami/vulndb/tree/main/data/rabbitmq/BIT-rabbitmq-2026-67218.json"
          }
        }
      ],
      "modified": "2026-10-20T10:30:04.688038978Z",
      "provider": "osv",
      "references": [
        "https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.6",
        "https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.0",
        "https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-34jw-rm7g-hph4",
        "https://nvd.nist.gov/vuln/detail/CVE-2026-67218"
      ],
      "provider_metadata": {
        "cpes": [
          "cpe:2.3:a:vmware:rabbitmq:*:*:*:*:*:*:*:*"
        ],
        "severity": "Medium"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2026-67218",
        "evidence": "/aliases"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/database_specific/severity"
  },
  "source_id": "core-osv",
  "document_id": 379072,
  "published_at": "2026-10-01T09:33:01.69+00:00"
}