CVE-2026-67220
published 2026-09-23CVE-2026-67220: RabbitMQ is a messaging and streaming broker. Prior to versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, 4.3.0, When a binding is created on an x-jms-topic exchange…
PriorityP341medium6.5CVSS 3.1
AVNACLPRLUINSUCNINAH
EPSS
0.31%
23.0th percentile
RabbitMQ is a messaging and streaming broker. Prior to versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, 4.3.0, When a binding is created on an x-jms-topic exchange, add_binding/3 reads the rjms_erlang_selector argument and passes it through erl_scan:string/1 then erl_parse:parse_term/1. erl_scan:string/1 interns every atom literal it tokenizes. validate_binding/2 is a no-op (-> ok.), there is no length cap, and the surrounding try/catch cannot reclaim atoms. The Java JMS client compiles selectors client-side, but the server does not enforce this , a raw AMQP client can send arbitrary selector strings. An authenticated low-privilege AMQP user confined to one vhost can crash the entire broker node (cross-tenant DoS) in <100 bind calls. Preconditions include rabbitmq_jms_topic_exchange plugin enabled (bundled; required for any JMS deployment) Authenticated AMQP user with read on an x-jms-topic exchange + write on a queue (or configure to declare both). This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, 4.3.0.
Affected
8 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| broadcom | rabbitmq_server | >= 3.13.0 < 3.13.15 | 3.13.15 |
| broadcom | rabbitmq_server | >= 4.0.0 < 4.0.20 | 4.0.20 |
| broadcom | rabbitmq_server | >= 4.1.0 < 4.1.11 | 4.1.11 |
| broadcom | rabbitmq_server | >= 4.2.0 < 4.2.6 | 4.2.6 |
| rabbitmq | rabbitmq-server | — | — |
| rabbitmq | rabbitmq-server | — | — |
| rabbitmq | rabbitmq-server | — | — |
| rabbitmq | rabbitmq-server | — | — |
CVSS provenance
nvdv3.16.5MEDIUMCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvdv4.06.0MEDIUMCVSS:4.0/AV:N/AC:L/AT:P/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
vendor_redhat6.0MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
rabbitmq-server: RabbitMQ: Denial of Service via JMS topic exchange atom exhaustion
vendor_redhat·2026-09-23·CVSS 6.0
CVE-2026-67220 [MEDIUM] CWE-770 rabbitmq-server: RabbitMQ: Denial of Service via JMS topic exchange atom exhaustion
rabbitmq-server: RabbitMQ: Denial of Service via JMS topic exchange atom exhaustion
RabbitMQ is a messaging and streaming broker. Prior to versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, 4.3.0, When a binding is created on an x-jms-topic exchange, add_binding/3 reads the rjms_erlang_selector argument and passes it through erl_scan:string/1 then erl_parse:parse_term/1. erl_scan:string/1 interns every atom literal it tokenizes. validate_binding/2 is a no-op (-> ok.), there is no length cap, and the surrounding try/catch cannot reclaim atoms. The Java JMS client compiles selectors client-side, but the server does not enforce this , a raw AMQP client can send arbitrary selector strings. An authenticated low-privilege AMQP user confined to one vhost can crash the entire broker node (cross-tenant DoS)
VulDB
RabbitMQ up to 3.13.14/4.0.19/4.1.10/4.2.5 JMS Topic Exchange erl_scan:string/erl_parse:parse_term rjms_erlang_selector denial of service
vuldb·2026-09-23·CVSS 6.0
CVE-2026-67220 [MEDIUM] RabbitMQ up to 3.13.14/4.0.19/4.1.10/4.2.5 JMS Topic Exchange erl_scan:string/erl_parse:parse_term rjms_erlang_selector denial of service
A vulnerability classified as problematic has been found in RabbitMQ up to 3.13.14/4.0.19/4.1.10/4.2.5. This affects the function erl_scan:string/erl_parse:parse_term of the component JMS Topic Exchange. This manipulation of the argument rjms_erlang_selector causes denial of service.
The identification of this vulnerability is CVE-2026-67220. It is possible to initiate the attack remotely. There is no exploit available.
It is recommended to upgrade the affected component.
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2026-67220 rabbitmq-server: RabbitMQ: Denial of Service via JMS topic exchange atom exhaustion [fedora-all]
bugzilla·2026-09-24·CVSS 6.0
CVE-2026-67220 [MEDIUM] CVE-2026-67220 rabbitmq-server: RabbitMQ: Denial of Service via JMS topic exchange atom exhaustion [fedora-all]
CVE-2026-67220 rabbitmq-server: RabbitMQ: Denial of Service via JMS topic exchange atom exhaustion [fedora-all]
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.
RabbitMQ is a messaging and streaming broker. Prior to versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, 4.3.0, When a binding is created on an x-jms-topic exchange, add_binding/3 reads the rjms_erlang_selector argument and passes it through erl_scan:string/1 then erl_parse:parse_term/1. erl_scan:string/1 interns every atom literal it tokenizes. validate_binding/2 is a no-op (-> ok.), there is no length cap, and the surrounding try/catch cannot reclaim atoms. The Jav
Bugzilla
CVE-2026-67220 rabbitmq-server: RabbitMQ: Denial of Service via JMS topic exchange atom exhaustion
bugzilla·2026-09-23·CVSS 6.0
CVE-2026-67220 [MEDIUM] CVE-2026-67220 rabbitmq-server: RabbitMQ: Denial of Service via JMS topic exchange atom exhaustion
CVE-2026-67220 rabbitmq-server: RabbitMQ: Denial of Service via JMS topic exchange atom exhaustion
RabbitMQ is a messaging and streaming broker. Prior to versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, 4.3.0, When a binding is created on an x-jms-topic exchange, add_binding/3 reads the rjms_erlang_selector argument and passes it through erl_scan:string/1 then erl_parse:parse_term/1. erl_scan:string/1 interns every atom literal it tokenizes. validate_binding/2 is a no-op (-> ok.), there is no length cap, and the surrounding try/catch cannot reclaim atoms. The Java JMS client compiles selectors client-side, but the server does not enforce this , a raw AMQP client can send arbitrary selector strings. An authenticated low-privilege AMQP user confined to one vhost can crash the entire broker node (cr
2026-09-23
Published