Skip to content
Heist/ feed
Back to feed
HighFix available

RabbitMQ: Stream Management Super-Stream Binding Keys Allocation Allows Low-Privilege Node Denial of Service

Type: advisorySources: OSV

RabbitMQ is a messaging and streaming broker. From 4.1.0 until 4.3.3, 4.2.9, and 4.1.11, Stream Management Super-Stream Binding Keys Allocation Allows Low-Privilege Node Denial of Service. rabbitMQ 4.3.1 with rabbitmqstreammanagement enabled accepts PUT /api/stream/super-streams/{vhost}/{name} requests from an authenticated management user that can access the target vhost. When the request body contains the binding-keys field, the handler parses the attacker-controlled comma-separated string and builds the full stream-name list before checking whether the user has permission to configure the resulting streams. A low-privileged management user with vhost access but no configure, write, or read permission can therefore force large transient allocations before the resource permission check. In a 768 MB memory-limited container, one HTTP PUT with about 4.5 MB of JSON body killed the RabbitMQ container with Docker state exited true An authenticated low-privileged management user can kill a memory-limited RabbitMQ node with one HTTP This issue is fixed in versions 4.3.3, 4.2.9, and 4.1.11.

Products
rabbitmq
Affected versions
Not specified
Fixed versions
4.1.11, 4.2.9, 4.3.3
CVEs
CVE-2026-67408
Confirmed fixed CVEs
Not specified
Updated in this feed
28 Oct 2026, 12:32 UTC · Revision 1

Source evidence

RabbitMQ: Stream Management Super-Stream Binding Keys Allocation Allows Low-Privilege Node Denial of Service

core-osv · Original source

Published 1 Oct 2026, 09:33 UTC

RabbitMQ is a messaging and streaming broker. From 4.1.0 until 4.3.3, 4.2.9, and 4.1.11, Stream Management Super-Stream Binding Keys Allocation Allows Low-Privilege Node Denial of Service. rabbitMQ 4.3.1 with rabbitmqstreammanagement enabled accepts PUT /api/stream/super-streams/{vhost}/{name} requests from an authenticated management user that can access the target vhost. When the request body contains the binding-keys field, the handler parses the attacker-controlled comma-separated string and builds the full stream-name list before checking whether the user has permission to configure the resulting streams. A low-privileged management user with vhost access but no configure, write, or read permission can therefore force large transient allocations before the resource permission check. In a 768 MB memory-limited container, one HTTP PUT with about 4.5 MB of JSON body killed the RabbitMQ container with Docker state exited true An authenticated low-privileged management user can kill a memory-limited RabbitMQ node with one HTTP This issue is fixed in versions 4.3.3, 4.2.9, and 4.1.11.

osv:BIT-rabbitmq-2026-67408

rabbitmq

Fixed versions: 4.1.11, 4.2.9, 4.3.3

Complete source record
{
  "id": "b6db732814c0a0324be3108bba0596238f26d84929fb23548b1e42cce5acf8a3",
  "url": "https://osv.dev/vulnerability/BIT-rabbitmq-2026-67408",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "RabbitMQ: Stream Management Super-Stream Binding Keys Allocation Allows Low-Privilege Node Denial of Service",
    "summary": "RabbitMQ is a messaging and streaming broker. From 4.1.0 until 4.3.3, 4.2.9, and 4.1.11, Stream Management Super-Stream Binding Keys Allocation Allows Low-Privilege Node Denial of Service. rabbitMQ 4.3.1 with rabbitmqstreammanagement enabled accepts PUT /api/stream/super-streams/{vhost}/{name} requests from an authenticated management user that can access the target vhost. When the request body contains the binding-keys field, the handler parses the attacker-controlled comma-separated string and builds the full stream-name list before checking whether the user has permission to configure the resulting streams. A low-privileged management user with vhost access but no configure, write, or read permission can therefore force large transient allocations before the resource permission check. In a 768 MB memory-limited container, one HTTP PUT with about 4.5 MB of JSON body killed the RabbitMQ container with Docker state exited true An authenticated low-privileged management user can kill a memory-limited RabbitMQ node with one HTTP This issue is fixed in versions 4.3.3, 4.2.9, and 4.1.11.",
    "evidence": "osv:BIT-rabbitmq-2026-67408",
    "products": [
      {
        "name": {
          "value": "rabbitmq",
          "evidence": "/affected/0/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "4.1.11",
            "evidence": "/affected/0/ranges"
          },
          {
            "value": "4.2.9",
            "evidence": "/affected/0/ranges"
          },
          {
            "value": "4.3.3",
            "evidence": "/affected/0/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "high",
    "structured": {
      "id": "BIT-rabbitmq-2026-67408",
      "aliases": [
        "BIT-rabbitmq-2026-67408",
        "CVE-2026-67408",
        "GHSA-2hm4-4438-49q8"
      ],
      "affected": [
        {
          "ranges": [
            {
              "type": "SEMVER",
              "events": [
                {
                  "introduced": "4.1.0"
                },
                {
                  "fixed": "4.1.11"
                },
                {
                  "introduced": "4.2.0"
                },
                {
                  "fixed": "4.2.9"
                },
                {
                  "introduced": "4.3.0"
                },
                {
                  "fixed": "4.3.3"
                }
              ]
            }
          ],
          "package": {
            "name": "rabbitmq",
            "purl": "pkg:bitnami/rabbitmq",
            "ecosystem": "Bitnami"
          },
          "severity": [
            {
              "type": "CVSS_V4",
              "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/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-67408.json"
          }
        }
      ],
      "modified": "2026-10-09T12:00:12.903672162Z",
      "provider": "osv",
      "references": [
        "https://github.com/rabbitmq/rabbitmq-server/commit/0f3defd176e027f54f447beee168d906d4f109b6",
        "https://github.com/rabbitmq/rabbitmq-server/commit/eb11bc44005fd6d327a78bf171bc598207778c9b",
        "https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.9",
        "https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.3",
        "https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-2hm4-4438-49q8",
        "https://nvd.nist.gov/vuln/detail/CVE-2026-67408"
      ],
      "provider_metadata": {
        "cpes": [
          "cpe:2.3:a:vmware:rabbitmq:*:*:*:*:*:*:*:*"
        ],
        "severity": "High"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2026-67408",
        "evidence": "/aliases"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/database_specific/severity"
  },
  "source_id": "core-osv",
  "document_id": 120700,
  "published_at": "2026-10-01T09:33:47.951+00:00"
}