{
  "id": "CVE-2026-67408",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-67408",
  "published_at": "2026-09-25T16:35:22.829Z",
  "title": "RabbitMQ: Stream Management Super-Stream Binding Keys Allocation Allows Low-Privilege Node Denial of Service",
  "vendor": "rabbitmq",
  "product": "rabbitmq-server",
  "cvss": {
    "score": 7.1,
    "source": "cna",
    "vector": "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"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": null,
  "description": "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.",
  "cwe": "CWE-400",
  "cpes": [
    "cpe:2.3:a:broadcom:rabbitmq_server:*:*:*:*:*:*:*:*"
  ],
  "cvss_by_source": {
    "cna": 7.1,
    "nvd": 6.5
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "rabbitmq",
        "product": "rabbitmq-server",
        "ranges": [
          "\u003e= 4.3.0, \u003c 4.3.3",
          "\u003e= 4.2.0, \u003c 4.2.9",
          "\u003e= 4.1.0, \u003c 4.1.11"
        ],
        "fixed_in": [
          "4.3.3",
          "4.2.9",
          "4.1.11"
        ]
      }
    ],
    "upgrade": [
      "Upgrade rabbitmq-server to 4.3.3 or 4.2.9 or 4.1.11 or later."
    ],
    "references": [
      {
        "kind": "Vendor advisory",
        "url": "https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-2hm4-4438-49q8"
      },
      {
        "kind": "Patch",
        "url": "https://github.com/rabbitmq/rabbitmq-server/commit/0f3defd176e027f54f447beee168d906d4f109b6"
      },
      {
        "kind": "Patch",
        "url": "https://github.com/rabbitmq/rabbitmq-server/commit/eb11bc44005fd6d327a78bf171bc598207778c9b"
      },
      {
        "kind": "Release notes",
        "url": "https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.9"
      },
      {
        "kind": "Release notes",
        "url": "https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.3"
      }
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
