{
  "affected": [
    {
      "ranges": [
        {
          "database_specific": {
            "extracted_events": [
              {
                "introduced": "4.2.0"
              },
              {
                "fixed": "4.2.7"
              },
              {
                "introduced": "4.3.0"
              },
              {
                "fixed": "4.3.1"
              }
            ],
            "source": [
              "AFFECTED_FIELD",
              "REFERENCES"
            ]
          },
          "events": [
            {
              "introduced": "95c501fbad76c66156346cf364d158d6e30aa4d9"
            },
            {
              "introduced": "1929eeadf9b2bac12c5434fb56884ef27370580e"
            },
            {
              "fixed": "b15fd2a3e5465cb6ed403d5a774ef61b1a391b89"
            },
            {
              "fixed": "49decca35e59d2cb774e5abd76412cee721308a5"
            }
          ],
          "repo": "https://github.com/rabbitmq/rabbitmq-server",
          "type": "GIT"
        }
      ]
    }
  ],
  "aliases": [
    "GHSA-x96j-244m-mrr2"
  ],
  "database_specific": {
    "cna_assigner": "GitHub_M",
    "cwe_ids": [
      "CWE-400"
    ],
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/67xxx/CVE-2026-67238.json"
  },
  "details": "RabbitMQ is a messaging and streaming broker. Prior to versions 4.2.7 and 4.3.1, rabbit_pid_codec:decompose_from_binary/1 parses a caller-supplied ETF-encoded binary and calls binary_to_atom(Node, utf8) on the node-name field. It is reached from rabbit_volatile_queue:pid_from_name/2, which is invoked for any queue name / routing key beginning amq.rabbitmq.reply-to.. The CandidateNodes membership check happens after the atom is created, and the surrounding try/catch cannot reclaim atoms (they are never GC'd). binary_to_existing_atom is not used. Any authenticated AMQP client can crash the entire Erlang VM (all vhosts, all connections) with ~1M cheap requests. Preconditions include Authenticated AMQP 0-9-1 connection to any vhost No per-connection rate limit low enough to make ~1M operations infeasible. This issue is fixed in versions 4.2.7 and 4.3.1.",
  "id": "CVE-2026-67238",
  "modified": "2026-09-26T03:30:39.235767825Z",
  "published": "2026-09-23T19:58:35.019Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.7"
    },
    {
      "type": "WEB",
      "url": "https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.1"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/67xxx/CVE-2026-67238.json"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-x96j-244m-mrr2"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-67238"
    }
  ],
  "schema_version": "1.9.0",
  "severity": [
    {
      "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",
      "type": "CVSS_V4"
    }
  ],
  "summary": "RabbitMQ: Atom-table exhaustion via reply-to queue name decoding"
}