BIT-rabbitmq-2026-67220
See a problem?- Import Source
- https://github.com/bitnami/vulndb/tree/main/data/rabbitmq/BIT-rabbitmq-2026-67220.json
- JSON Data
- https://api.osv.dev/v1/vulns/BIT-rabbitmq-2026-67220
- Aliases
-
- CVE-2026-67220
- GHSA-r3qr-4h63-mvj2
- Published
- 2026-10-01T09:33:06Z
- Modified
- 2026-10-01T10:11:06Z
- Summary
- RabbitMQ: JMS topic exchange erl_scan atom exhaustion
- Details
-
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.
- Database specific
{ "cpes": [ "cpe:2.3:a:vmware:rabbitmq:*:*:*:*:*:*:*:*" ], "severity": "Medium" }- References
Affected packages
Bitnami / rabbitmq
Package
- Name
- rabbitmq
- Purl
- pkg:bitnami/rabbitmq
Severity
- 6.0 (Medium) CVSS_V4 - CVSS: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 CVSS Calculator