A flaw in the JMS topic exchange implementation allows an authenticated AMQP user to submit a selector string that the server parses with Erlang’s scanner and parser. The scanner interns every atom literal it encounters, with no length limit, causing the atom table to be exhausted and the broker to crash. The result is a cross‑tenant denial of service that can be triggered with fewer than 100 binding operations.

RabbitMQ Server versions prior to 3.13.15, 4.0.20, 4.1.11, 4.2.6 and 4.3.0 that have the bundled rabbitmq_jms_topic_exchange plugin enabled. An authenticated AMQP user with read access to an x-jms-topic exchange and write access to a queue (or the ability to declare both) is required to exploit the issue.

The vulnerability carries a CVSS score of 6.0, indicating moderate severity. The EPSS score is not available and the flaw is not listed in the CISA KEV catalog. An attacker who can obtain low‑privilege AMQP credentials, or who can craft raw AMQP traffic, can exploit the defect through a relatively simple binding sequence, leading to a broker crash within a short burst of operations.