{
  "cveId": "CVE-2026-67419",
  "url": "https://patchblox.com/security/cve/CVE-2026-67419",
  "summary": "CVE-2026-67419 is fixed in rabbitmq-server on 1 platform by DEBIAN-CVE-2026-67419 (version 4.3.6-1), released October 10, 2026. It is not reported as exploited. Patch Radar priority: Routine.",
  "title": "RabbitMQ: Consecutive topic wildcards cause combinatorial routing work",
  "description": "RabbitMQ is a messaging and streaming broker. Prior to 4.3.5, an authenticated user who can bind a queue to a topic exchange and publish to it can use consecutive # segments in a binding key to make both topic matchers revisit the same trie-node and routing-key-suffix states without memoization. The matcher materializes duplicate destinations before deduplication, causing combinatorial CPU work and memory pressure that can disrupt routing for all tenants. This vulnerability is fixed in 4.3.5.",
  "published": "2026-09-25T17:17:13Z",
  "severity": "Important",
  "cvss": 6.5,
  "cvssVector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
  "cwe": "Inefficient Algorithmic Complexity",
  "epss": 0.00373,
  "epssPercentile": 0.31424,
  "priority": "Routine",
  "priorityTier": 4,
  "exploited": false,
  "vendorExploited": false,
  "disclosed": false,
  "vendorAdvisory": "https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-67419",
  "fixes": [
    {
      "platform": "linux",
      "product": "rabbitmq-server",
      "release": "Debian 14",
      "fixedVersion": "4.3.6-1",
      "fix": "DEBIAN-CVE-2026-67419",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2026-67419",
      "released": "2026-10-10T22:48:57Z"
    }
  ],
  "noFixYet": [],
  "dataAsOf": "2026-11-08T13:06:02Z",
  "attribution": {
    "text": "Data: Patchblox Patch Radar",
    "url": "https://patchblox.com/security/patch-radar",
    "terms": "https://patchblox.com/security/patch-radar/use-the-data"
  }
}